Hi,
Now I have tried to restart the resilvering by detaching c9t7d0 and then
attaching it again to the mirror, then the resilvering starts but now
after almost 24 hours it is still going.
From the iostat it still shows data flowing:
tank-nfs 446G 2,28T 112 8 13,5M 35,9K
mirror 145G 783G 107 2 13,4M 12,0K
c9t6d0 - - 106 2 13,3M 12,0K
c9t7d0 - - 0 110 0 13,4M
$zpool status -xv
pool: tank-nfs
state: ONLINE
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
scrub: resilver in progress for 23h23m, 100,00% done, 0h0m to go
config:
NAME STATE READ WRITE CKSUM
tank-nfs ONLINE 0 0 0
mirror ONLINE 0 0 0
c9t6d0 ONLINE 0 0 0
c9t7d0 ONLINE 0 0 0 1,02T resilvered
This time as you can see it is 0 checksum errors during the resilvering.
Is it something with the build I am using ? (118)
--
Rasmus Fauske
Markus Kovero skrev:
We've noticed this behaviour when theres problem with ram (plenty of checksum
errors) and on these cases I doubt resilver will ever finnish, you can use
iostat to monitor if theres anything happening on disk that should be
resilvered, if not, Id say data wanted to resilver is somehow gone bad due
broken ram or who knows.
(this is actually resilver and checksumming working as it should, no data that
is not valid should be written)
Yours
Markus Kovero
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
