From owner-freebsd-current@FreeBSD.ORG Sun Jan 6 22:32:41 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AE7916A475 for ; Sun, 6 Jan 2008 22:32:41 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.org [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 0F9FC13C469 for ; Sun, 6 Jan 2008 22:32:41 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from c-75-75-30-250.hsd1.va.comcast.net ([75.75.30.250]:64993 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1JBe2p-0001g3-Sy for freebsd-current@freebsd.org; Sun, 06 Jan 2008 22:32:40 +0000 Message-ID: <47815705.1010006@conducive.net> Date: Sun, 06 Jan 2008 22:32:37 +0000 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20080106141157.I105@fledge.watson.org> <47810DE3.3050106@FreeBSD.org> <478119AB.8050906@FreeBSD.org> <47814160.4050401@samsco.org> <478148FD.20605@FreeBSD.org> <47814E20.70801@samsco.org> In-Reply-To: <47814E20.70801@samsco.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS honesty X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2008 22:32:41 -0000 Scott Long wrote: *trimmed* > > 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