Scott Long wrote:

*trimmed*

quoted text
> 
> I guess what makes me mad about ZFS is that it's all-or-nothing; either
> it works, or it crashes.  It doesn't automatically recognize limits and
> make adjustments or sacrifices when it reaches those limits, it just
> crashes.  Wanting multiple gigabytes of RAM for caching in order to
> optimize performance is great, but crashing when it doesn't get those
> multiple gigabytes of RAM is not so great, and it leaves a bad taste in
> my mouth about ZFS in general.
> 
> Scott

To be fair - every fs on the planet had to go through this at one time or another.

We have been perhaps 'spoiled' by the odd runaway log or such that has pushed 
UFS to over 103% 'full', struggled on regardless, allowing us to ssh in from 
12,000 miles away, kill the offender, clean up the mess, and soldier-on w/o even 
a reboot, let alone a crash.

ZFS will (probably) get there one day as well.

But at present, it has become a distraction we don't need.

We're chasing promises...

I'd happily trade all future interest in ZFS for better ufs, nfs, smbfs, ntfs, 
xfs, jfs, et al performance/safety/compatibility,

... if only 'coz that's where the bulk of the data we need to 'talk to' actually 
resides - not on ZFS or GPFS.

Bill


_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"