On 2016-04-13 18:46, Andrei Borzenkov wrote:
Also even if hibernation image is preserved, if LinuxA tries to access any filesystem of LinuxB, it gets corrupted.
Yes, I was going to say this. It gets awfully corrupted, in fact, beyond repair most times. In fact, during hibernation grub disables the boot menu, so that the user can not choose a different system to boot to avoid precisely this scenario. I don't see an advantage to creating another swap. If wanted, it must be a manual and intentional choice, and another for presenting grub menu after hibernation. Long explanation: When trying to mount a filesystem belonging to an hibernated machine (A), the (B) system sees it as dirty and does an fsck on it, which probably succeeds. But (A) has a memory image of what should be that mounted filesystem, with files opened and half written. When it comes out of hibernation, at some time it will write those files to the blocks it would have used previously, not matching what (B) did with the fsck. The result is awful corruption. I know this from personal experience. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)