If this is a non-root pool which is not available at boot, then you should do
this:
sudo zpool set cachefile=none POOL
That will inhibit the creation of a zpool.cache file for that pool.
The other option, if this is always plugged in, would be to configure it
to unlock automatically on boot. For example, using a key file. This
would be secure only if the root file system is also on LUKS.
** Changed in: zfs-linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624844
Title:
Ubuntu 16.04 breaks boot with wrong zpool.cache
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1624844/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
