Public bug reported:
The backport of upstream commit 68dde63d138882860109178f4ab0b7b1b1bb3cfd in
0.8.3-1ubuntu14 is not correct for the 0.8.3 stable series and causes an oops
on boot with a 5.7 kernel. The patch that shipped in 0.8.4 is slightly
different, and works correctly:
https://github.co
I've attached my workaround script. To use:
change the ZFSPOOLNAME variable in the script to the name of the zfspool with
an NVMe L2ARC.
change the NVMEL2ARCPART to the name of the cache partition.
sudo cp zpool-offline-cache.sh /lib/systemd/system-sleep/
sudo chmod +x /lib/systemd/system-sleep/
That info is from:
zpool status -v
I've worked around this suspend issue by writing a script to take the
NVMe L2ARC cache offline during suspend, and bring it back online on
resume.
The issue with bcache on suspend that I had for a similar situation is
because a read can trigger a write to the ca
I am also seeing this issue with zfs and l2arc cache on an NVMe and
4.10.14 on zesty. I've seen it in the past with btrfs, and a bcache
cache on NVMe as well, but not with the bcache cache on a SATA SSD. I
will move my zfs l2arc cache to a SATA SSD to see if that fixes suspend.
This is probably an
4 matches
Mail list logo
