Darren J Moffat wrote:
Jorgen Lundman wrote:
Jorgen Lundman wrote:
However, "zpool detach" appears to mark the disk as blank, so
nothing will find any pools (import, import -D etc). zdb -l will
show labels,
For kicks, I tried to demonstrate this does indeed happen, so I dd'ed
the first 1024 1k blocks from the disk, zpool detach it, then dd'ed
the image back out to the HDD.
Pulled out disk and it boots directly without any interventions. If
only zpool detach had a flag to tell it not to scribble over the
detached disk.
This is a known issue. The simple case is actually quite easy (and I
had nearly working code for it pretty quickly). What I mean by the
simple case is 2 disks in a mirror. What if it was actually a 4 disk
or 48 disk pool setup as mirrored pairs - that is much harder to deal
with. Or the cases where there are cache and log devices in the pool
make it harder to deal with as well (not really an issue for root
pools though).
Maybe the 2 disk mirror is a special enough case that this could be
worth allowing without having to deal with all the other cases as
well. The only reason I think it is a special enough cases is because
it is the config we use for the root/boot pool.
Not so much a 2 disk mirror, but a single vdev mirror (e.g. also a 3-way
mirror, having one split off).
This is asked for by multiple customers at every ZFS Discovery Day we do.
See 6849185 and 5097228.
--
Andrew
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
