>>>>> "cm" == Courtney Malone <[EMAIL PROTECTED]> writes:
cm> # zpool detach data 17096229131581286394
cm> cannot detach 17096229131581286394: no valid replicas
I think detach is only for mirrors. That slot in the raidz stripe has
to be filled with some kind of marker, even if the drive is not
present, because the raidz slots aren't interchangeable like they are
in a mirror. With raidz{,2} you're supposed to be able to 'zpool
offline' up to the redundancy limit, but not detach.
cm> # zpool replace data 17096229131581286394 c0t2d0
cm> cannot replace 17096229131581286394 with c0t2d0: cannot replace a
replacing device
That's frustrating. This hasn't happened to me yet.
How about:
# zpool replace data 11342560969745958696 c0t2d0
Maybe one of the two UUID's is the original and one's the copy, and
you have to restart the replacement by referring to the original not
the copy?
If that doesn't work, maybe you've hit a corner case that's not
well-handled. 'zpool replace' should be interruptable without
corruption, and maybe not need to be abortable but at least needs to
be restartable. Let us know what happens.
pgpdZNX1Dzkjp.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
