Hi George, Sorry for covering the basics again. Diagnosis by email is difficult.
Which OpenSolaris release is this? Are you saying that the resilver never completes (possibly, really slow) or it restarts again when you run the zpool status command? I found this bug: http://bugs.opensolaris.org/view_bug.do?bug_id=6655927 zpool status causes a resilver or scrub to restart However, from your output it looks like the resilver is restarting whether you are e...@solaris $ or e...@solaris #. Is the e...@solaris $ a privileged user? Thanks, Cindy G. Mola wrote:
Cindy, I did that, now resilvering starts up again. e...@solaris:~# zpool clear distroclips c5d0 e...@solaris:~# zpool status pool: distroclips state: DEGRADED 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 0h2m, 0.66% done, 5h15m to go config: NAME STATE READ WRITE CKSUM distroclips DEGRADED 0 0 0 raidz1 DEGRADED 0 0 0 c4d0 ONLINE 0 0 0 1.76M resilvered replacing DEGRADED 0 0 0 c5d0s0/o FAULTED 0 932 0 corrupted data c5d0 ONLINE 0 0 0 4.65G resilvered c4d1 ONLINE 0 0 0 1.74M resilvered c5d1 ONLINE 0 0 0 1.68M resilvered errors: No known data errors Thanks again. GeorgeGeorge, Rerun the zpool clear command like this: # zpool clear distroclips c5d0 Even though the zpool status command below exposes the c5d0[s0] with the slice info, the disk name is c5d0. Cindy
_______________________________________________ sysadmin-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
