If this is a non-root pool which is not available at boot, then you should do 
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.

  Ubuntu 16.04 breaks boot with wrong zpool.cache

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to