Bug 213676

Summary:	Items missing from 11.0 Release Notes
Product:	Documentation	Reporter:	Kurt Lidl <lidl>
Component:	Books & Articles	Assignee:	Glen Barber <gjb>
Status:	Closed FIXED
Severity:	Affects Some People	CC:	emaste
Priority:	---
Version:	Latest
Hardware:	Any
OS:	Any

Description Kurt Lidl freebsd_committer

2016-10-21 14:45:42 UTC

A friend who upgraded a system from 10.3, which previously ran various 10.x
releases, and was originally installed probably as a 9.0 system.

Always upgraded via freebsd-release.

Anyhow - successfully upgrade to 11.0 Release, and commented that two items
that were not documented in the release notes that probably should be
noted for people planning to upgrade.

Both issues are ZFS related:

1) The new support for sha512 and skein checksums in a zpool was not
   documented.  This is important in that 'zpool status' (after upgrading)
   will complain that the zpool version is out of date until
   'zpool upgrade -a' is run.

   A possible improvement to the code (outside the scope of this issue), would
   be to have a mechanism to have the acknowledge of the feature, but warning
   suppression.

   If the user DOES do a 'zpool upgrade -a', they then need to install fresh
   bootblocks.  Which leads to item #2...

2) The increased size of the /boot/gptzfsloader in 11.0 vs prior releases.
   The machine in question was installed probably with 9.0, when the 'best
   practices' was to have a 64k boot partition.  Well, the gptzfsloader code
   is now ~88K, and does not fit in the existing partition.

   A warning about potentially needing a bigger freebsd-boot partition is
   required for people upgrading older releases, least they upgrade their
   zpool and then be stuck without the ability to upgrade their bootblocks.

   (As it turns out the user was able to reclaim a 'gap' in the partitioning
   and get the bootblocks upgraded without having to reload the system from
   scratch.)

Comment 1 Glen Barber freebsd_committer

2016-10-21 14:51:46 UTC

*** Bug 213675 has been marked as a duplicate of this bug. ***

Comment 2 Kurt Lidl freebsd_committer

2016-10-21 14:52:36 UTC

Here's a sample of the message for the 'zpool status' output, from one of my systems that was installed as a 10.x host, and then upgraded to 11/stable:

lidl@gatekeeper-141: zpool status
  pool: sys
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
	still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
	the pool may no longer be accessible by software that does not support
	the features. See zpool-features(7) for details.
  scan: scrub repaired 0 in 0h17m with 0 errors on Mon Oct 17 04:16:59 2016
config:

	NAME        STATE     READ WRITE CKSUM
	sys         ONLINE       0     0     0
	  mirror-0  ONLINE       0     0     0
	    da0a    ONLINE       0     0     0
	    da1a    ONLINE       0     0     0

errors: No known data errors

Comment 3 Kurt Lidl freebsd_committer

2016-10-21 14:58:08 UTC

Compared to a machine where the zpool has been upgraded:

root@hydra-353: zpool status
  pool: sys
 state: ONLINE
  scan: scrub repaired 0 in 1h32m with 0 errors on Fri Oct 14 05:11:35 2016
config:

	NAME          STATE     READ WRITE CKSUM
	sys           ONLINE       0     0     0
	  mirror-0    ONLINE       0     0     0
	    gpt/sys0  ONLINE       0     0     0
	    gpt/sys1  ONLINE       0     0     0

errors: No known data errors

Comment 4 Kurt Lidl freebsd_committer

2016-10-21 15:02:24 UTC

Clarificatio:

Always upgraded via freebsd-update.

Comment 5 Glen Barber freebsd_committer

2016-10-21 18:04:55 UTC

Documented.  I forgot to reference the PR in the commit.