Linux

56892 readers

692 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

multi boot - Hibernating and booting into another System or Distribution: will my filesystems be corrupted? (superuser.com)

submitted 11 hours ago* (last edited 4 hours ago) by HaraldvonBlauzahn@feddit.org to c/linux@lemmy.ml

7 comments fedilink hide all child comments

Short answer is: yes, as soon as more than one OS mounts a file system in read-write mode.

The kernel of a modern OS (I am generously including Windows here) caches file system data structures in memory. When you hibernate the computer, the content of that memory is written into a large file because that speeds-up a later restart.

Now, if you boot up another OS, and modify these partitions (without mounting them read-only), you alter the file systems data structures. That happens already when you view folders because this modifies access times stored in the inodes.

When you now shut down the second OS, and resume the first OS, the restarted kernel will have and use cached file system metadata which id loaded from the image into the kernel, that does not match that of the files on disk. And this causes file system corruption by definition.

you are viewing a single comment's thread
view the rest of the comments

[–] HaraldvonBlauzahn@feddit.org 4 points 4 hours ago* (last edited 4 hours ago)

No, I mean hibernate, with the PC turned off. In sleep state, you return to the running kernel/OS, so no possibility to boot into another distro, therefore no risk of filesystem damage.

The crucial thing is that file systems need to be unmounted before they can be accessed by another distribution or OS.

see

https://askubuntu.com/questions/55527/dual-boot-and-sleep-hibernate-issues