On 2013-08-31 02:45, Harry Putnam wrote:
My last two paragraphs are thinking I will have created a 3 part
mirror of rpool ... The newest member is over twice the size of the
other two.
So I'm suggesting I should detach the big one once it is silvered and
made bootable.
You've explained what happens when that detach happens but in this
case I would be detaching a third member of the mirror which would
leave a mirrored pair of bootable discs. I guess the same thing would
happen with them?
So once rebooted (Assuming I can emergency boot or something to see
what happened to my user or its password), I asked if I could then
make rpool grow onto the bigger disc by using the `autoexpand'
property?
No, I believe that if you "zfs detach" the bigger disk, it would become
an ex-member of a pool, but not importable as a pool. See "zfs split"
for a way to make independent pools by breaking up a mirror, but note
that I've only heard of this tool mode and did not actually use it :)
If this works the way I expect of it, then you'd be able to make a pool
made of the big disk and then autoexpand (or possibly "zfs attach -e")
to its whole size. It is possible that in order for expansion to happen
you'd also have to use "format" and/or "fdisk" to make sure that the
big disk's MBR partition and s0 slice cover as much space as they can
(i.e. not in a layout identical to the one on two smaller disks).
HTH,
//Jim Klimov
_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss
