Note for those pulling in new ZFS feature flags

[Chris Nehren]

On Mon, Apr 07, 2014 at 15:36:21 +0100, Tom Evans wrote:
> > I solved this by re-running `gpart bootcode` for the afflicted
> > drives.  This was a bit trying, though, as my workstation is the
> > only FreeBSD machine I have readily available.  So, for those
> > upgrading their zpools, be careful and remember to fix the
> > bootcode if you're using ZFS for the root filesystem.
> 
> ISTR that "zpool upgrade" will also remind you to do this if bootfs is
> true for the pool you upgraded.
> 
> Also, it is always worth having around a bootable memstick available
> with the zfs code you are actually running in order to use as a
> recovery disk in circumstances like this.

I'm fairly certain there was no such message, or I would have
dutifully done what it said.  I definitely do know there is a
message of that kind when attaching a disk to a mirror, and I've
followed through there without issue.

-- 
Chris Nehren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 919 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20140407/6b78247f/attachment.sig>