https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277886
Tomoaki AOKI <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Tomoaki AOKI <[email protected]> --- You are stating about loader, so I'll intentionally ignore here about features not supported by features unsupported after boot (not implemented in zfs.ko, used AFTER kernel starts). For features supported by zfs.ko but not by loader (zfsloader, loader.efi), unsupported featres are categorized into 2. 1. Read-only compatible feature 2. Features not in 1. For case 1, loader can (theoretically) sanely read the pool. So should run sanely even if they are enabled and active. For case 2, if the features are enabled but not yet set to active and actually used, theoretically loader can still read and boot the pool. But once any of the features are actually used, loader no longer can read it. For example, if new hash function which loader doesn't support is activated and used, loader cannot calculate the hash to check whether the file (/boot/loader.conl, kernel itself, ...) is broken or not. As broken files SHALL not be used to boot. The only solution for case 2 is to implement the unspported feature into loader. But if your complaints are about case 1, loader.should be fixed. -- You are receiving this mail because: You are the assignee for the bug.
