On Sat, Mar 27, 2010 at 6:02 PM, Harry Putnam <rea...@newsguy.com> 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. That exactly the kind of problem ZFS is designed to catch. > > Is there specific documentation somewhere that tells how to read these > status reports? > Your pool is not degraded so I don't think anything will show up in fmdump. But check 'fmdump -eV' and see the actual errors that got created. You could find something there. -- Giovanni
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
