Date: Mon, 20 Oct 2008 11:37:13 -0700 From: Xin LI <delphij@delphij.net> To: Jeremy Chadwick <koitsu@FreeBSD.org> Cc: freebsd-stable@freebsd.org, JoaoBR <joao@matik.com.br> Subject: Re: constant zfs data corruption Message-ID: <48FCCFD9.70807@delphij.net> In-Reply-To: <20081020171927.GB8551@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> <45836B9A-CB6E-4B95-911E-0023230B8F82@mac.com> <20081020171927.GB8551@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeremy Chadwick wrote: [snip] > 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. Also when copies >= 2. This is very useful for e.g. laptops. I have set copies=2 for all zfs file systems (not on the whole pool) storing important personal data (/home, /usr/src), and after 3 times (!) of hard drive bad sector incidents (all replaced after recoverdisk) within 6 months, I was very lucky not to use the last resort by restoring data from my monthly DVD-R backup. Cheers, - -- Xin LI <delphij@delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkj8z9kACgkQi+vbBBjt66CdBwCeO+ADiDOzAjcG4w16AJkOaUo4 xskAnRPVynvvVWWfMm2zd/T2KGB4/s2U =M2aF -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48FCCFD9.70807>