On 3/25/19 8:15 AM, Josh Paetzel wrote: > Portability of boot pools is currently not a consideration.
Dealing with this for boot pools is a serious and timely concern of mine. I use Ubuntu, which uses GRUB. It is clear that, in practice, GRUB is not going to be kept up-to-date with new OpenZFS features in a timely fashion, if ever. (I'm not laying any blame, just stating the reality.) Limiting one's pool to only features supported by GRUB is increasingly frustrating; that rules out the upcoming native encryption, for example. Accordingly, I have updated the Ubuntu Root-on-ZFS HOWTO to use a separate "bpool" with restricted features for /boot. This allows "rpool" for / to have all the features (or portable features or whatever someone wants). Ubuntu itself is seriously investigating root-on-ZFS, so I'd like to find a solution to the problem that `zpool upgrade` wants to "upgrade" the "bpool" into a broken state by enabling features that GRUB does not support. If the portable definitions are in a text file, it will be really easy to support `zpool create -o features=grub`. It's only slightly harder if it's compiled in. But I would like to have a definition for GRUB in my distro, even if it isn't in upstream ZoL or OpenZFS/Illumos. It may actually be desirable for this to be in the distro packaging, such that it can match the version from GRUB. Or if this used a .d directory of multiple text files, it could actually be part of the GRUB distro package rather than the ZFS distro package. -- Richard ------------------------------------------ openzfs: openzfs-developer Permalink: https://openzfs.topicbox.com/groups/developer/Td66d70a086ae5a9e-M6365380f429030e4e433da61 Delivery options: https://openzfs.topicbox.com/groups/developer/subscription
