Hey folks,
While scrubbing, zpool status shows nearly 40MB "repaired" but 0 in each of the
read/write/checksum columns for each disk. One disk has "(repairing)" to the
right but once the scrub completes there's no mention that anything ever needed
fixing. Any idea what would need to be repaired on that disk? Are there any
other types of errors besides read/write/checksum? Previously, whenever a disk
has required repair during scrub it's been either bad disk or loose cable
connection and it's generated read, write and/or cksum errors. It also irks me
a little that these repairs are only noted while the scrub is running. Once
it's complete, it's as if those repairs never happened.
If it's relevant, this is a 6 drive mirrored pool with a single SSD for L2Arc
cache. Pool version 26 under Nexenta Core Platform 3.0 with a LSI 9200-16E and
SATA disks.
$ zpool status bigboy
pool: bigboy
state: ONLINE
scan: scrub in progress since Sat Feb 5 02:22:18 2011
3.74T scanned out of 3.74T at 141M/s, 0h0m to go
37.9M repaired, 99.88% done
[-----config snip - all columns 0, one drive on the right has "(repairing)"----]
errors: No known data errors
And then once the scrub completes:
$ zpool status bigboy
pool: bigboy
state: ONLINE
scan: scrub repaired 37.9M in 7h42m with 0 errors on Sat Feb 5 10:04:53 2011
[-----config snip - all columns 0, the "(repairing)" note is now gone----]
errors: No known data errors
--
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
