that you can write to, eject the disk before entering hibernation, then reboot into the other OS to use the data.
#Mac os cannot unmount disk zip#
If you want to safely exchange data between any mutation of Windows and any other OS while Windows is in hibernation (note that this will apply to more than Windows being in hibernation) then what certainly works correctly (note: I do this myself) is to use a removable volume, such as a Jaz drive (I’ve got one of those) or a Zip drive, etc. The *only* way you can be assured that things won’t get mangled up in terms of using a filesystem that was used by the OS that’s currently in hibernation from the other one is to unmount the filesystem, as that will completely close out all handles to files on it, and leave the filesystem in a perfect state, and leave no dangling applications that were expecting things to be the way they were in the previous clock cycle. The gory details of what is stored in the filesystem cache while in hibernation mode really isn’t that important: regardless, if you hibernate and use the filesystem from within another OS effectively between clock cycles of the OS in hibernation, you run the risk of hosing up the system horribly. Journalling doesn’t prevent data loss, however, it just guarantees that the FS will always be in a consistent state. That is quite literally a braindead thing to do.Īs for EXT3/NTFS … yeah, they’re journalled. You should NOT be using the same file system at the “same time” with two different operating systems, mounted twice. Linux will try to correct the file system because it’s been marked as dirty - this can lead to any number of other problems. Suddenly the data is in different places, and programs in Windows may crash the moment they try to work with an open file.
Certain files might be changed that are still open over in Windows. Suddenly what Windows remembers in terms of a FAT table is wrong. You then boot into Linux, and start making changes.
You hibernate Windows, and none of this changes. File system is marked as dirty (not unmounted). File seek points are in certain places.Ĥ. Some files are open, and expected to be in a certain state.ģ. You have no idea what you’re talking about.
0 kommentar(er)
