>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 the caching device. Currently bcache has no good ways of
solving this. This means resume must finish before bcache starts.
However, if the resume image is on the bcache backing device, the image
must be accessed first. Using resume_offset to use the swap file on the
backing device must be updating the caching device, and subsequently
causing data loss. If I have reached the correct conclusion from the
data loss that occured on my system and the limitation listed on the
bcache FAQ, then that means swap files are not supported on bcache
period. With that in mind, bcache should not allow hibernation to occur
using swap files.

-- 
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:
  Backing device unattaches from caching device when hibernating into a
  swap file

To manage notifications about this bug go to:
https://bugs.launchpad.net/bcache-tools/+bug/1878340/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to