I want to warn/bug-report/ask about how an ext3 partition got destroyed and the policy considered best to prevent it.
In 12.3 x64, root partition a, while some files were opened on partition x, I clicked hibernate and booted from another hdd, 12.3 x68. Some data written to, and even shrinked some % partition x. Then a while later, no more aware about hibernation, booted from partition a again, noticing resume and geany asking wether it should reload a textfile. I noticed the textfile data was lost, fsck x reported “partitiontable or superblock corrupted”, month work to recover partition x.
I suspect the resumed session writing to partition x having corrupted the superblock. I think that won’t happen to me again. I intend to edit the grub2menu-entry to not resume from disk in such a situation.
If a resume from disk really can destroy a partition, I suggest to developers to make OpenSUSE more foolproof with a function to prevent this issue. A brainstorm: if it is not already so, flush data to disk before hibernation; after resume from disk, reopen files or check for altered metadata, filepositions; or mark a grubmenu-entry “hibernated”, warn users for this issue and present an easier option to reboot without resume.
What do you guys and girls consider the best policy to prevent this happening to others?
Sofar my 2 cents.