From owner-freebsd-fs@FreeBSD.ORG Thu Apr 23 22:19:14 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A60A1065677; Thu, 23 Apr 2009 22:19:14 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 094CD8FC08; Thu, 23 Apr 2009 22:19:14 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (adsl-67-215-2.shv.bellsouth.net [98.67.215.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 7034D8006B37; Thu, 23 Apr 2009 17:19:12 -0500 (CDT) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id n3NMItGP026717; Thu, 23 Apr 2009 17:19:07 -0500 (CDT) (envelope-from morganw@chemikals.org) Date: Thu, 23 Apr 2009 17:18:55 -0500 (CDT) From: Wes Morgan To: Ivan Voras In-Reply-To: Message-ID: References: <49F048FB.6000401@bqinternet.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 metadata checksums X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2009 22:19:14 -0000 On Thu, 23 Apr 2009, Ivan Voras wrote: > Scott Burns wrote: > >> 2) Is there a demand for this in FreeBSD? > > Speaking for myself, I'd like it on the systems I maintain. (I'd also > like a sysctl to ignore the errors, just in case :) ). That's actually something ZFS could use if you ask me. In one instance I had some bad ram that was causing checksum errors (zfs is better than memtest for finding bad ram!), and I had to comment out the ECHKSUM error from the kernel to recover the pieces of the file that were reported corrupt.