On 2015-11-08 07:07, John Andersen wrote:
On 11/07/2015 07:54 PM, Carlos E. R. wrote:
I have not tried this on purpose either, but I think it has happened to me a couple times and the system detected that the image in swap was not valid for the system being booted.
Ah! So there is a signature. Yes, make sense. I think I remember reading about it.
It simply reverts to a fresh boot, which will destroy (overwrite) your swap image, an you loose any work in progress in the swap image.
Ugh. It should revert to "abort", or "ask".
I don't know what constitutes the signature of that suspend file in swap.
See this page: http://unix.stackexchange.com/questions/123547/can-swap-be-shared-safely-whi...
Yes, a different swap would work (partially), except that it is not my workcase :-) (partially, because I would probably mount partitions that are already opened, and dirty, on the "other" boot, so they would be fsck-ed. And when later starting the hibernated partition, this would try to use the sleeping partitions, with files in opened state, but which was fsck-ed... The result is horrible corruption, I can tell you. It happened to me, quite some years ago.) My use case is that I simply have a multiboot machine, and one of the boots is the default, but that one may not be the one I last used and which I want again. I can not use hibernate on the other boots unless I remember to select it the next time. Which I probably will not :-} -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)