Hi Will,
I simulated this issue on s10u7 and then imported the pool on a
current Nevada release. The original issue remains, which is you
can't remove a spare device that no longer exists.
My sense is that the bug fix prevents the spare from getting messed
up in the first place when the device IDs change, but after the original
device is removed, you can't remove the spare. I think the only
resolution is to put the device back and then you can remove the spare.
This was my resolution during testing.
But, in your case, the original device is renamed.
I don't think the ghost spare causes a problem except aesthetically.
I'm no expert in this error scenario so I will check with someone else
(when he gets back from vacation and then I'm on vacation).
Thanks,
Cindy
On 08/04/09 18:34, Will Murnane wrote:
On Tue, Aug 4, 2009 at 19:05, <cindy.swearin...@sun.com> wrote:
Hi Will,
It looks to me like you are running into this bug:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6664649
This is fixed in Nevada and a fix will also be available in an
upcoming Solaris 10 release.
That looks like exactly the problem we hit. Thanks for Googling for me.
This doesn't help you now, unfortunately.
Would it cause problems to temporarily import the pool on an
OpenSolaris machine, remove the spare, and move it back to the Sol10
machine? I think it'd be safe provided I don't do "zpool upgrade" or
anything like that, but I'd like to make sure.
Thanks,
Will
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
