I had a similar problem a little while ago. While it is probably not
"the right way" to do it, I forced this by unplugging the new drive and
rebooting. Then, making sure that the zvol was clean except for the
missing drive, I powered down, connected the new drive, and powered up
again. I was then able to re-attach the new drive and all was well.
A rescrub cannot be initiated under certain instances. This caused a
catch-22 for me as it did for you. It would be nice to override this, if
any ZFS developers are listening.
Rainer
On 3/28/2010 2:31 PM, Jim wrote:
I had a drive fail and replaced it with a new drive. During the resilvering
process the new drive had write faults and was taken offline. These faults were
caused by a broken SATA cable (drive checked with Manufacturers software and
all ok). New cable fixed the the failure. However, now the drive shows as
faulted.
I know the drive is healthy so want to force a rescrub. However, this wont happen while
it is showing FAULTED. I tried to force a replace but this gives the error "Cannot
replace a replacing device". So I seem to be in a stuck state, where the replace
wont complete. Please help - screen output below.
C3P0# zpool status
pool: tank
state: DEGRADED
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
tank DEGRADED 0 0 0
raidz1 DEGRADED 0 0 0
ad4 ONLINE 0 0 0
ad6 ONLINE 0 0 0
replacing UNAVAIL 0 1.06K 0 insufficient
replicas
1796873336336467178 UNAVAIL 0 1.23K 0 was /dev/ad7/old
4407623704004485413 FAULTED 0 1.22K 0 was /dev/ad7
errors: No known data errors
C3P0# zpool replace -f tank 4407623704004485413 ad7
cannot replace 4407623704004485413 with ad7: cannot replace a replacing device
C3P0#
--
Mind the Gap
Web: http://www.dragonhearth.com
Blog: http://chaos.dragonhearth.com
_______________________________________________
sysadmin-discuss mailing list
sysadmin-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
