Public bug reported:
This behavior is very inconsistent. I'm using btrfs, which only recently
received swap file support as of linux kernel version 5.0. I followed
the directions to get a swap file working on btrfs, including using
resume=swap_device and resume_offset=swap_file_offset. The
** Description changed:
This behavior is very inconsistent. I'm using btrfs, which only recently
received swap file support as of linux kernel version 5.0. I followed
the directions to get a swap file working on btrfs, including using
resume=swap_device and resume_offset=swap_file_offset.
In that case, I've reported this bug to the wrong place. This is a
bcache specific issue and not a distro specific issue. I'm not exactly
sure where to report it now. I apologize for this mistake.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Actually, a proposed solution that could work is disabling the caching
device on bcache before hibernating. See here for more details:
https://bcache.evilpiepirate.org/FAQ/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From looking deeper into this issue and reading the FAQ on the bcache
site, this appears to be a catch 22 issue. During resume, you are not
allowed to make any changes to the disk. However, with bcache, this can
be tricky: any read you make from a bcache device could result in a
write to update
