From owner-freebsd-stable@FreeBSD.ORG Mon Oct 20 17:52:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E1F910656A0; Mon, 20 Oct 2008 17:52:37 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout022.mac.com (asmtpout022.mac.com [17.148.16.97]) by mx1.freebsd.org (Postfix) with ESMTP id 55F0E8FC13; Mon, 20 Oct 2008 17:52:37 +0000 (UTC) (envelope-from cswiger@mac.com) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from cswiger1.apple.com ([17.227.140.124]) by asmtp022.mac.com (Sun Java(tm) System Messaging Server 6.3-7.03 (built Aug 7 2008; 32bit)) with ESMTPSA id <0K9100HHHTLLYC40@asmtp022.mac.com>; Mon, 20 Oct 2008 10:52:21 -0700 (PDT) Message-id: <73C3E69D-07EC-4266-87AB-97E37D0EED1C@mac.com> From: Chuck Swiger To: Jeremy Chadwick In-reply-to: <20081020171927.GB8551@icarus.home.lan> Date: Mon, 20 Oct 2008 10:52:21 -0700 References: <200810171530.45570.joao@matik.com.br> <200810200837.40451.joao@matik.com.br> <20081020132208.GA3847@icarus.home.lan> <98238FC8-0FC4-4410-829F-EF2EA16A57B8@mac.com> <20081020164831.GA8016@icarus.home.lan> <45836B9A-CB6E-4B95-911E-0023230B8F82@mac.com> <20081020171927.GB8551@icarus.home.lan> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable@freebsd.org, JoaoBR Subject: Re: constant zfs data corruption X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2008 17:52:37 -0000 On Oct 20, 2008, at 10:19 AM, Jeremy Chadwick wrote: >> He's not getting working filesystem redundancy with the existing >> config >> and is vulnerable to losing data from a single drive failure, agreed. >> But the ZFS checksum mechanism should still be working to detect data >> corruption, even though ZFS cannot recover the corrupted data the >> way it >> otherwise would if redundancy was available. > > Ahh, I see. So to paraphrase, ZFS can detect checksum errors (data > corruption) using any pool type (single disk, mirror, raidz, > whatever), > but can only *repair* the error when using a mirror or raidz. I think that should be the case, yes. Regards, -- -Chuck