Ubuntu 22.04: Update bpool features

This brings in things from Debian Bullseye.

Signed-off-by: Richard Laager <rlaager@wiktel.com>
This commit is contained in:
Richard Laager
2022-05-19 22:48:30 -05:00
parent c084a2ebff
commit bc3af3ba58

View File

@@ -287,8 +287,10 @@ Step 2: Disk Formatting
-o feature@filesystem_limits=enabled \
-o feature@hole_birth=enabled \
-o feature@large_blocks=enabled \
-o feature@livelist=enabled \
-o feature@lz4_compress=enabled \
-o feature@spacemap_histogram=enabled \
-o feature@zpool_checkpoint=enabled \
-O acltype=posixacl -O canmount=off -O compression=lz4 \
-O devices=off -O normalization=formD -O relatime=on -O xattr=sa \
-O mountpoint=/boot -R /mnt \
@@ -329,12 +331,16 @@ Step 2: Disk Formatting
boot pool. If one cares about speeding up the boot pool, it would make
more sense to put the whole pool on the faster disk rather than using it
as a ``special`` vdev.
- The ``device_rebuild`` feature should be safe to use (except on raidz,
which it is incompatible with), but the boot pool is small, so this does
not matter in practice.
- The ``log_spacemap`` and ``spacemap_v2`` features have been tested and
are safe to use. The boot pool is small, so these do not matter in
practice.
- The ``project_quota`` feature has been tested and is safe to use. This
feature is extremely unlikely to matter for the boot pool.
- The ``resilver_defer`` should be safe but the boot pool is small enough
that it is unlikely to be necessary.
- The ``spacemap_v2`` feature has been tested and is safe to use. The boot
pool is small, so this does not matter in practice.
- As a read-only compatible feature, the ``userobj_accounting`` feature
should be compatible in theory, but in practice, GRUB can fail with an
“invalid dnode type” error. This feature does not matter for ``/boot``