Date: Sun, 20 Dec 2009 06:54:48 -0500 From: Thomas Burgess <wonslung@gmail.com> To: Attila Nagy <bra@fsn.hu> Cc: freebsd-fs@freebsd.org Subject: Re: Plans for Logged/Journaled UFS Message-ID: <deb820500912200354q56bb4662u781cac8a7811d5f0@mail.gmail.com> In-Reply-To: <4B2E0FA9.1050003@fsn.hu> References: <20091030223225.GI5120@datapipe.com> <4AEB6D79.5070703@feral.com> <4B2E0FA9.1050003@fsn.hu>
next in thread | previous in thread | raw e-mail | index | archive | help
I think it depends on hardware and setup. I've noticed the "zfs problem" with SOME machines when it comes to rtorrent (the rtorrent process will be stuck "waiting for disk" but on other machines it's fine. The machines i've had the most problem with are single drive less than 2 gb ram. I've got rtorrent and zfs working fine on plenty of machines with 2-3 hard drives and 4-8 gb ram. On Sun, Dec 20, 2009 at 6:51 AM, Attila Nagy <bra@fsn.hu> wrote: > Matthew Jacob wrote: > >> Hussain Ali wrote: >> >>> >>> ZFS doesnt suffice for may use cases - so just wondering if this is in >>> the works. >>> >>> >>> >> Which use cases can you name? >> > Reliable data storage. :( > > Sadly, ZFS in FreeBSD is still very far from being stable. For example I > have NFS servers running on ZFS, and they freeze about every week. It seems > it's related to NFS. > I can't even get to the debugger. After sending an NMI, the kernel writes > "NMI ... going to debugger" eight times (those machines have 8 CPU cores) > and nothing happens, I can only reset. > > Another machine just looses ZFS access (all processes stuck in IO) on i386 > if I run rtorrent with unlimited bandwidth with some torrents, or some disk > intensive spam filtering. Access to UFS filesystems are still OK. > > Also, running UFS and ZFS seems to have problems in 8-STABLE with UFS > eating out memory from ZFS. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?deb820500912200354q56bb4662u781cac8a7811d5f0>