Subject: Re: Data corruption issues possibly involving cgd(4)
To: Nino Dehne <ndehne@gmail.com>
From: Daniel Carosone <dan@geek.com.au>
List: current-users
Date: 01/17/2007 07:23:19
--huq684BweRXVnRxX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jan 16, 2007 at 08:36:15AM +0100, Nino Dehne wrote:
> On Tue, Jan 16, 2007 at 08:28:35AM +0100, Bernd Ernesti wrote:
> > Can you check the s.m.a.r.t. status of your drives?
> >=20
> > atactl wdX smart status
>=20
> They all check fine. Besides, what would happen if raid(4) got fed a
> corrupted block? I'm under the impression I would see more serious errors
> far earlier than observing silent data corruption several layers above, n=
o?
Actually, no. raid(4) doesn't check parity unless it gets an error;
you want zfs for that..
And if it does turn out to be power, the corruption induced could be
happening a number of places, including some (like main memory) which
SMART won't see.
--
Dan.
--huq684BweRXVnRxX
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (NetBSD)
iD8DBQFFrTQ3EAVxvV4N66cRAmemAJ4o1Ly88UksAvj0djp7qiuIiLIrdwCbB/X5
/kfZ5ApF0cf2FXPgUJPrIXY=
=UCur
-----END PGP SIGNATURE-----
--huq684BweRXVnRxX--