Date: Mon, 20 Oct 2008 15:18:01 -0200 From: JoaoBR <joao@matik.com.br> To: Chuck Swiger <cswiger@mac.com> Cc: Jeremy Chadwick <koitsu@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: constant zfs data corruption Message-ID: <200810201518.01678.joao@matik.com.br> In-Reply-To: <45836B9A-CB6E-4B95-911E-0023230B8F82@mac.com> References: <200810171530.45570.joao@matik.com.br> <20081020164831.GA8016@icarus.home.lan> <45836B9A-CB6E-4B95-911E-0023230B8F82@mac.com>
index | next in thread | previous in thread | raw e-mail
On Monday 20 October 2008 15:03:14 Chuck Swiger wrote: > 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. > all right and understood but shouldn't something as fsck should correct the error? Seems kind of problematic to me mounting zfs in single user mode, deleting the file and restarting the OS ? -- Joćo A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.brhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200810201518.01678.joao>