loader should ignore active multi_vdev_crash_dump feature on zpool
Currently the new bootloader ("loader") won't mount a zpool with the multi_vdev_crash_dump feature active (i.e. you have an actual dump zvol on the pool using it). Since the loader doesn't need to touch the zvol in question, it should be safe to just make it ignore it by adding it to features_for_read in zfsimpl.c.
Tested this by building it in staging and pulling it down onto a box that boots from its zpool. The box has no usb key, so it boots from a kernel+boot_archive stored in the pool at /zones/boot/*.
- Pulled down new gptzfsboot and zfsloader, installed with the installboot command
- Rebooted, machine comes up and mounts the pool correctly to find the kernel, where previously zfsloader bailed out with an "unsupported pool feature" message
Updated by Electric Monk over 4 years ago
- Status changed from New to Closed
commit 6f8e6e5e0a44293205c7f187c667f9c9afa40795 Author: Alex Wilson <email@example.com> Date: 2018-02-18T19:46:03.000Z 9051 loader should ignore active multi_vdev_crash_dump feature on zpool Reviewed by: Patrick Mooney <firstname.lastname@example.org> Reviewed by: Jerry Jelinek <email@example.com> Reviewed by: Yuri Pankov <firstname.lastname@example.org> Reviewed by: Toomas Soome <email@example.com> Approved by: Richard Lowe <firstname.lastname@example.org>