On 1/22/10 4:05 PM, Shawn Walker wrote: > On 01/22/10 05:02 PM, Frank Allan wrote: >> Darren, Ethan >> >> one other point about different ZFS pools which I haven't seen mentioned >> in this thread is that ZFS versions are continuing to change, and if >> (for example) b125 supports ZFS version 12 and b130 supports version 15, >> then if you have both in the same pool, the ZFS version needs to be >> maintained at the lower level or else b125 can't use it. >> >> I am unsure how this is handled currently. If you have a new BE >> installed which supports the later version and you do 'zpool upgrade' do >> you get a warning that you will not be able to use the older BEs in this >> pool (if this is in fact the case).
You do not get a warning from the zpool upgrade command that is specific to BE's however the user is warned that the pool may not be available to earlier versions of ZFS. Since older BE's are by definition older versions of ZFS they may not be bootable. This behavior is pretty well documented and is the same for both beadm and live upgrade on Solaris 10. >> >> If upgrading the pool makes earlier BEs unavailable it would seem there >> may need to be some interaction between zfs and beadm commands to make >> sure the user is aware of the consequences. There is a notice when you >> run 'zpool upgrade' that the pool may not be available to earlier >> versions of ZFS, but it is unclear whether this affects the other BEs in >> this pool. I suspect it would. The fact that the user does get this warning and that they know older BE's are on the older zpool version it's pretty clear that upgrading the pool can leave these older BE's unbootable. It should not however make them completely inaccessible, I believe the user should still be able to mount them. >> >> Is this being addressed anywhere? Does it need to be? > > This is also an important consideration when considering manipulation of > boot environments using beadm. Can beadm create/destroy/list boot > environments regardless of the original zpool build, and what > dependencies does the installer have on that functionality? Yes beadm can still manipulate these BE's but if a BE contains an older build that doesn't not support the newer zpool version that BE will not be bootable. I think the main functionality that the installer uses if be_init for creating an empty BE to install into and be_list to list existing BE's. -evan
