From owner-freebsd-fs@FreeBSD.ORG Wed Aug 6 16:41:06 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 157F5643 for ; Wed, 6 Aug 2014 16:41:06 +0000 (UTC) Received: from eddie.gameowls.com (eddie.gameowls.com [IPv6:2001:470:1f11:3e8::214]) by mx1.freebsd.org (Postfix) with ESMTP id EA91525A9 for ; Wed, 6 Aug 2014 16:41:05 +0000 (UTC) Received: from [IPv6:2001:470:c412:beef:135:a9e:3ef5:fbe7] (unknown [IPv6:2001:470:c412:beef:135:a9e:3ef5:fbe7]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by eddie.gameowls.com (Postfix) with ESMTPSA id 3D28A11FA613 for ; Wed, 6 Aug 2014 11:40:59 -0500 (CDT) From: Joseph Love Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: MooseFS client crash on FreeBSD 10 Message-Id: <7F032402-F79E-4AF7-90E9-DE90AA0E2D76@getsomewhere.net> Date: Wed, 6 Aug 2014 11:40:59 -0500 To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Aug 2014 16:41:06 -0000 Hi, I=92ve been experimenting with MooseFS, trying to get a good impression = of it=92s performance in my environment, but I=92ve been running into = issues with the client running on FreeBSD 10 (system information = towards the end of this email). Performance seems a bit dismal, but the = big thing is that the mfsmount client eventually crashes: pid 1004 (mfsmount), uid 0: exited on signal 6 (core dumped) I=92ve tried both MooseFS 1.6.27 out of the ports collection as well as = MooseFS 2.0 (provided by the MooseFS developers, as something to try). I can definitely repeat the crash using iozone. The output in iozone = ends like this: 16384 512 28179 63377 6005999 6037129 5984033 = 364032 3236019 369825 5940580 60282 405846 4500939 4482736 16384 1024 32297 58530 6122653 6079322 6014409 = 379364 3791669 351158 8752060 58609 412757 4326386 4543494 16384 2048 Error writing block 0, fd=3D 3 write: Input/output error iozone: interrupted Anyway, I=92m just hoping that someone might have an idea for = determining if it=92s an issue with the FUSE module in FreeBSD 10, or = something else going on with MooseFS. Or, just a well, if=20 someone has run into this issue and solved it! I=92d normally just think it=92s a MooseFS thing, but it=92s obviously = in the ports collection, and the MooseFS client running on a mac seems = to work fine, and iozone reports better write (but not better random = write) performance - some of which I think is caching. System information: 3x Chunkservers & MooseFS Master: Dual Xeon 5500 series, 24gb memory, = ZFS on root, ZFS dataset for MooseFS, 2x 1tb WD Se (in ZFS stripe), = Intel S3500 SSD for ZIL. FreeBSD 10-Release-p7. Client 1: FreeBSD 10-release-p7 in a VM. 4gb memory, 4 cores on an i7. Client 2: (testing at different times than client 1) Mac OS 10.9. If anyone has any ideas to try, I=92d love to hear them. Thanks, -Joe=