John wrote:
I was able to solve it, but it actually worried me more than anything.
Basically, I had created the second pool using the mirror as a primary device.
So three disks but two full disk root mirrors.
Shouldn't zpool have detected an active pool and prevented this? The other LDOM
was claiming a corrupted device, which I was able to replace and clear easily.
But the one pool I originally posted about looks to be permanently gone, since
it believes there is another device, but doesn't know where the device is or
what it was ever called. If I could import it and re-do the mirror somehow, or
something similar, it'd be great. Is there anyway to force it to realize it's
wrong?
You can try limiting access to one device at a time by removing one device from
LDOM configuration, or creating separate directory like /tmp/dsk and copying
symlink for the device you want to try there and trying to do
zpool import (if device is removed at the LDOM level)
zpool import -d /tmp/dsk (in case you prefer trick with symlinks)
Posting label 0 (from zdb -l /dev/rdsk/... output) of both involved disks may
provide more clues.
regards,
victor
Obviously, I should've kept better track of the WWN's - But I've made the
mistake before and zpool always prevented it.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
