-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-23 a las 14:52 +0100, Peter Suetterlin escribió:
Carlos E. R. wrote:
On 2018-02-23 09:59, Peter Suetterlin wrote:
Per Jessen wrote:
I thought I would do a full reinstall this time - just server pattern on a xen guest. I noticed the partitioner did not automatically re-use an existing swap parittion, but opted to carve a new one out.
I'd call it the safe way. Could be the existing one contains a hibernated system?
Formatting the swap partition of an hibernated system will cause it to crash, and corrupt all the partitions it was using.
Nitpicking: It's not running, so it can hardly crash :D
Well, it not be able to thaw at all.
While yes, it's likely leaving unclean partitions, I'd expect the hibernate script also to do something like a sync before, so damage should be small. Better than just switching off the power/pressing reset, which most systems handle quite well these days.
No, hibernate does not sync the filesystems. But I was mistaken: erasing the swap partition in that case is similar to hitting the power button.
Normally, a computer that is hibernated will not allow to boot any other system, including the install DVD/stick.
What? TBH, this is the first time I ever hear this. And I *have* booted hibernated systems with a different OS. Quite some time ago though - I'm exclusively using suspend nowadays.
You have been lucky. Situation. You have a running system, and it hibernates. The filesystems remain open, files half written, some structures in ram, which are swapped, not flushed. Then you boot a second system in the same machine, and it mounts some or all the "hibernated" partitions. It thinks that the partitions are dirty, not cleanly umounted (as if the power button was hit), so it fscks the filesystems. Perhaps some files are written to those. Then thys system powers off. Next the first filesystem thaws. It thinks that the filesystems are in the state *it* left them, but they aren't. It writes the in memory structures to disk *in its previous unrepaired status*. The resulting destruction on those filesystems is epic. It happened to me, just once, so I know.
If the partitioner finds an hibernation image it should abort.
NACK, by all means.
I might very well know what I'm doing. Just aborting and refusing to work is exactly the kind of Windows-typical behavior that I do **NOT** want to see on Linux.
A clear warning is fine. Everything else is not
Nope. Abort. :-) If you know what you are doing, issue a command line undocumented option that allows you to continue. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlqQU+QACgkQja8UbcUWM1y+9QEAjNN++7Zv3sXWNjkcpEEchbjS DFY1hJ6nR3iDXm5dIbIBAIPwHWhCogEW8Pal5XIAJgKGjIrfz3XzfHIrDcTmSshN =SzLq -----END PGP SIGNATURE-----