On 03/31/10 10:42 AM, Frank Middleton wrote:
On 03/31/10 12:21 PM, lori.alt wrote:
The problem with splitting a root pool goes beyond the issue of the
zpool.cache file. If you look at the comments for 6939334
<http://monaco.sfbay.sun.com/detail.jsf?cr=6939334>, you will see other
files whose content is not correct when a root pool is renamed or split.
6939334 seems to be inaccessible outside of Sun. Could you
list the comments here?
Thanks
Here they are:
Other issues:
* Swap is still pointing to rpool because /etc/vfstab is never updated.
* Likewise, dumpadm still has dump zvols configured with the original pool.
* The /{pool}/boot/menu.lst (on sparc), and /{pool}/boot/grub/menu.lst (on x86)
still reference the original pool's bootfs. Note that the 'bootfs' property in
the pool itself is actually correct, because we store the object number and not
the name.
While each one of these issues is individually fixable, there's no way to
prevent new issues coming up in the future, thus breaking zpool split. It
might be more advisable to prevent splitting of root pools.
*** (#2 of 3): 2010-03-30 18:48:54 GMT+00:00mark.musa...@sun.com
yes, these looks like the kind of issues that flash archive install had to
solve: all the tweaks that need to be made to a root file system to get it to
adjust to living on different hardware. In addition to the ones listed above,
there are all the device specific files in /etc/path_to_inst, /devices, and so
on. This is not a trivial problem. Cloning root pools by the split mechanism
is more of a project in its own right. Is zfs split good for anything related
to root disks? I can't think of a use. If there is a need for a disaster
recovery disk, it's probably best to just remove one of the mirrors (without
doing a split operation) and stash it for later use.
*** (#3 of 3): 2010-03-30 20:21:57 GMT+00:00lori....@sun.com
Lori
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
