On 03/28/10 10:02 AM, Harry Putnam wrote:
Bob Friesenhahn<bfrie...@simple.dallas.tx.us> writes:
On Sat, 27 Mar 2010, Harry Putnam wrote:
What to do with a status report like the one included below?
What does it mean to have an unrecoverable error but no data errors?
I think that this summary means that the zfs scrub did not encounter
any reported read/write errors from the disks, but on one of the
disks, 7 of the returned blocks had a computed checksum error. This
could be a problem with the data that the disk previously
wrote. Perhaps there was an undetected data transfer error, the drive
firmware glitched, the drive experienced a cache memory glitch, or the
drive wrote/read data from the wrong track.
If you clear the error information, make sure you keep a record of it
in case it happens again.
Thanks.
So its not a serious matter? Or maybe more of a potentially serious
matter?
Not really. The error has been corrected.
Is there specific documentation somewhere that tells how to read these
status reports?
If you run a scrub on a pool and an error condition is fixed, the report
wil give you a URL to check.
--
Ian.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
