From owner-freebsd-questions@FreeBSD.ORG Thu Jun 21 14:52:29 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7B718106566C for ; Thu, 21 Jun 2012 14:52:29 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99]) by mx1.freebsd.org (Postfix) with ESMTP id DE3548FC19 for ; Thu, 21 Jun 2012 14:52:28 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id q5LEqPXA003296; Thu, 21 Jun 2012 16:52:26 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id q5LEqPbW003293; Thu, 21 Jun 2012 16:52:25 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Thu, 21 Jun 2012 16:52:25 +0200 (CEST) From: Wojciech Puchar To: Eduardo Morras In-Reply-To: <4FA8826F00BC43C3@> (added by postmaster@resmaa12.ono.com) Message-ID: References: <4FA8826F00BC43C3@> (added by postmaster@resmaa12.ono.com) User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Thu, 21 Jun 2012 16:52:26 +0200 (CEST) Cc: freebsd-questions@freebsd.org Subject: Re: Is ZFS production ready? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 14:52:29 -0000 > > With UFS2 you can use file systems up to 2^73 (8 ZB). The problem is not UFS, > but the old tools used to format the disk like fdisk and bsdlabel. For big > file systems you must use gpart. true. or not using anything at all (and put filesystem directly on whole device/mirror). > The problem with file system recovery times when "the worst thing > happens"(tm) is soluted/mitigated with su+j on FreeBSD9. True but i don't believe completely in SU+J. i use it - eg on my private backup disk. but do full fsck sometimes. and usually few, but nonzero amount of errors are corrected. but with just SU it is easy to solve. Disable fsck on boot at all. softupdates allow that risk without problems. then do fsck at time when full or partial system outage can be tolerated - after work hours. This is my solution used everywhere. of course fsck on 100TB filesystem will be too slow. But it is implementation problem, and could be improved. but i would not recommend making single virtual device (gmirror/gstripe or dedicated hardware matrix controller) from too many disks because of the risk.