From owner-freebsd-questions@FreeBSD.ORG Wed Jun 11 18:35:15 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF6F21065680 for ; Wed, 11 Jun 2008 18:35:15 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 543178FC26 for ; Wed, 11 Jun 2008 18:35:13 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.2/8.14.2) with ESMTP id m5BIZ8MD073154 for ; Wed, 11 Jun 2008 20:35:08 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.2/8.14.2/Submit) with ESMTP id m5BIZ8Xm073151 for ; Wed, 11 Jun 2008 20:35:08 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Wed, 11 Jun 2008 20:35:08 +0200 (CEST) From: Wojciech Puchar To: freebsd-questions@freebsd.org In-Reply-To: <200806111757.m5BHvZXI066360@lurza.secnetix.de> Message-ID: <20080611202926.X73093@wojtek.tensor.gdynia.pl> References: <200806111757.m5BHvZXI066360@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: FreeBSD + ZFS on a production server? 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: Wed, 11 Jun 2008 18:35:15 -0000 > Wojciech Puchar wrote: > > 3) a CPU,cache and memory bandwidth hogging "feature" of checksumming all > > blocks. thing that are already done in disk hardware. fortunately you can > > turn this off > > Obviously you have been lucky to never be a victim of > silent disk corruption (or you just haven't noticed). what you mean. that disk wrote the data wrong and doesn't detect it on read? i would mean broken disk processor, it's memory etc. possible - as much as broken main processor, main memory, some of chips on motherboard etc. - which will make ZFS calculate checksum wrong on write, or even calculate checksum right of wrong data generated by badly operating programs. given the complexity of motherboard+CPU etc. to complexity of disk hardware, i don't think "silent disk failure" happens often. i think all your cases wasn't disk, but general hardware problems. ZFS may help detect it, or it may not. if it helped for you. even without ZFS it WOULD cause problems with programs like random crashes. personally i often got disk failing the way that it was unable to read or write giving an error, but never things like that. > You're free to use UFS, of course, and keep suffering > from its shortcomings. i have to start suffering at first....