MooseFS client crash on FreeBSD 10
Joseph Love
joe at getsomewhere.net
Wed Aug 6 16:41:06 UTC 2014
Hi,
I’ve been experimenting with MooseFS, trying to get a good impression of it’s performance in my environment, but I’ve 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’ve 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= 3
write: Input/output error
iozone: interrupted
Anyway, I’m just hoping that someone might have an idea for determining if it’s an issue with the FUSE module in FreeBSD 10, or something else going on with MooseFS. Or, just a well, if
someone has run into this issue and solved it!
I’d normally just think it’s a MooseFS thing, but it’s 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’d love to hear them.
Thanks,
-Joe
More information about the freebsd-fs
mailing list