I'm wondering why Solaris is reporting
action: Wait for the resilver to complete. scan: resilver in progress since Sun Jul 14 02:42:44 2013 24.9T scanned out of 39.2T at 54.9M/s, 75h46m to go 24.9T scanned out of 39.2T at 54.9M/s, 75h46m to go 908G resilvered, 63.56% done
39.2T is the size of the complete pool, which is built from 4 raidz1 vdevs:
config: NAME STATE READ WRITE CKSUM volume ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ... raidz1-1 ONLINE 0 0 0 ... raidz1-2 ONLINE 0 0 0 ... raidz1-3 ONLINE 0 0 0 ...
and every raidz1 has 7 disks x 2TB.
So, IIUC, the resilvering would have to go over <= 6x2TB to reconstruct the data of a single failed disk. How comes ZFS is scanning over the whole pool? I thought the redundant data needed for resilvering is not stored across multiple raidzs?
Thank you for explanation!