Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    The errors already happened, so even if you could - it would not solve your problem. The filesystem state already deviates (in-memory vs. on-disk) so you'd end up with even more corruption issues. Commented Apr 15, 2022 at 19:04
  • 2
    That said if you freeze it beforehand (cryptsetup luksSuspend) so all I/O is halted, and then make sure the device is operational in some fashion, you may be able to tinker it with dmsetup, for example - but it's dangerous to do these things. No idea if it can be done properly. Ideally the kernel should make sure that all devices are re-established on resume... I don't use suspend/resume at all for this reason, there are way too many things that can go wrong to be worth it... Commented Apr 15, 2022 at 19:23
  • Your use case is one that security software explicitly guards against. "Change my underlying media and try to use the same authentication? It's a trick! " Commented Apr 16, 2022 at 1:38