Dan,
I see now how you might have created this config.
I tried to reproduce this issue by creating a separate pool on another
disk and a volume to attach to my root pool, but my system panics when
I try to attach the volume to the root pool.
This is on Nevada, build 130.
Panic aside, we don't currently recommend building pool components on
top of other pool components because deadlocks can occur.
Cindy
On 01/11/10 19:00, Daniel Carosone wrote:
On Tue, Jan 12, 2010 at 02:38:56PM +1300, Ian Collins wrote:
How did you set the subdevice in the off line state?
# zpool offline rpool /dev/zvol/dsk/....
sorry if that wasn't clear.
Did you detach the device from the mirror?
No, because then:
- it will have to resilver fully on next attach, no quick update
- it will be marked detached, and harder to import for recovery. I'm
not even sure it can be easily recovered, maybe with import -D?
If I do detach the subdevice, of course then the external pool can be
exported - but that's not helpful for the original goal. If I
shutdown ungracefully, and boot without the external disk attached,
the expected components are faulted, but again that's not especially
desirable for normal operations.
Perhaps the new "zpool split" will be better for the second issue,
but won't address the first issue. One of the several reasons for
wanting to use a zvol (or file on zfs) is to be able to clone the
backing store for an "import -f" while keeping the original for
further incremental resilvers.
--
Dan.
------------------------------------------------------------------------
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
