On 27/08/2020 19:51, Brandon Bergren wrote: > FWIW, on powerpc64, using /etc/zfs/zpool.cache is great because it avoids the > problem of having to unmount /boot (which is an msdos filesystem because > peitiboot doesn't understand ufs or zfs) to update the copy of zpool.cache > that is on the root filesystem in /boot instead of only changing the one in > the runtime /boot (which was mounted on top, and is never useful because it's > not mounted at the time that zpool.cache is actually needed to import pools.) > > In any case, the correct way on ZFS to control where the cachefile is written > is to set the cachefile property on the zpool to the specific path. The > correct behavior regarding boot time auto import of pools is to honor that > property as found on the pool the boot filesystem was on, so that other pools > sharing the same cachefile path will be imported. Multiple cache files and > pools not actually listed in a cachefile are valid scenarios for pools.
Just want to express my complete agreement. -- Andriy Gapon _______________________________________________ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
