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
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=207809.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Also affects: bcache-tools via
https://bugzilla.kernel.org/show_bug.cgi?id=207809
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878340
Title:
No need to apologize, it can be complex at times.
We can be glad you reported it at all instead of just being grumpy about it :-)
Bcache is "at home" at https://bcache.evilpiepirate.org/
It seems it uses ther kernel style for bugs which means:
tracker:
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
Hi and thanks for taking the time to report this bug.
There isn't really enough information here for a developer to confirm
this issue is a bug, or to begin working on it, so I am marking this bug
Incomplete for now.
Given that the setup you are trying to achieve is rather non-standard,
I'm
** 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.
