Date: Mon, 20 Oct 2008 10:03:14 -0700 From: Chuck Swiger <cswiger@mac.com> To: Jeremy Chadwick <koitsu@FreeBSD.org> Cc: freebsd-stable@freebsd.org, JoaoBR <joao@matik.com.br> Subject: Re: constant zfs data corruption Message-ID: <45836B9A-CB6E-4B95-911E-0023230B8F82@mac.com> In-Reply-To: <20081020164831.GA8016@icarus.home.lan> References: <200810171530.45570.joao@matik.com.br> <E3C2EAB9-12ED-4D3E-B07A-E2FF5892D26A@mac.com> <200810200837.40451.joao@matik.com.br> <20081020132208.GA3847@icarus.home.lan> <98238FC8-0FC4-4410-829F-EF2EA16A57B8@mac.com> <20081020164831.GA8016@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 20, 2008, at 9:48 AM, Jeremy Chadwick wrote: > Hm... I thought we determined earlier in this thread that the OP is > not > getting the benefits of ZFS checksums because he's not using raidz > (only > a single disk with a single pool)? 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. Regards, -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45836B9A-CB6E-4B95-911E-0023230B8F82>