Hi Rainer,
This is a long thread and I wasn't commenting on your previous
replies regarding mirror manipulation. If I was, I would have done
so directly. :-)
I saw the export-a-pool-to-remove-a-disk-solution described in
a Sun doc.
My point and (I agree with your points below) is that making a pool
unavailable to remove a disk is not a good administrative practice if
you are unclear of the impact on the overall health of the original
pool.
Currently, if what you really want is to remove a disk from a
redundant pool, then better options are zpool detach or zpool replace.
Cindy
Rainer Heilke wrote:
Nenad,
I've seen this solution offered before, but I would
not recommend this
except as a last resort, unless you didn't care about
the health of
the original pool.
This is emphatically not what was being requested by me, in fact. I agree, I
would be highly suspicious of the data's integrity depending upon the zpool
structure.
There are a couple other things to consider. First, this requires exporting the whole pool, which
automatically assumes an outage is acceptable. Second, it assumes the other half of the mirror will be used
elsewhere as in "on another system". This is also not a fair automatic assumption to make. The
comments I made in this thread (I can't speak for others) were that the broken-off mirror may be used safely
elsewhere, with the understanding this could even be on the same system, perhaps for archival reference or
some-such. "Elsewhere" does not automatically imply "on another server". My apologies if
I did not make this clear.
Rainer
This message posted from opensolaris.org
_______________________________________________
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
