Hi Cindy,
No problem at all.. I do appreciate all your help and I know how difficult is
it through email.
Version:
SunOS solaris 5.11 snv_101b i86pc i386 i86pc
OpenSolaris 2008.11 with updates
Resilvering seems to be completing (unless it dies at the last second, when
0h00m left), but if I r
George,
Another option mentioned in the bug report is to ignore the resilvering
progress by not using zpool status to see if it finishes (working around
the zpool status bug).
If its not the zpool status bug that's causing this resilver to loop, then
I would check the hardware, make sure the di
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.or
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.
Hi Cindy,
Thank you for your response.
I was also referring to the automatic ZFS snapshots, for the "distroclips"
zpool, although I did not terminate the other snapshots. (I am not using any
hardware-level snapshot.)
This morning I turned off the box for a few hours (to prevent the endless
"
George,
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
G. Mola wrote:
Hi Cindy,
Thank you for your response.
I was also referring to the automatic ZFS
George,
Are you referring to hardware-level snapshots?
Ben is referring to automatic ZFS snapshots that are running in the
OpenSolaris release.
To be sure, what is the output of this command:
% zfs list -t snapshot
Thanks,
Cindy
G. GOMOLA wrote:
Update: I have stopped the snapshots for
