On Friday 30,October,2009 02:32 AM, Roger Binns wrote: > Note that there are important differences between these. For the file > cache there is good reason to drop it. For example lets say you have an > NTFS partition mounted, hibernate, boot into Windows (using the NTFS > partition) and then reboot/resume back into Linux. If Linux continued > to use previously cached information then it will trash the NTFS > partition. And yes this really happened to me when I used suspend2 as > TuxOnIce used to be known. Something similar would happen if you booted > into a LiveCD and messed with existing hard disk contents (note that > rescue mode likes to mount up everything you have). In this case I > would much rather Ubuntu erred on the side of caution. I've learnt this the hard way before, but with swsusp (current method used in Ubuntu), not TuxOnice/Suspend2, and using a vfat partition. I hibernated Windows and booted into Ubuntu and vice versa. Next thing I knew, the paths were all messed up (I had files with / in their names, and had to use photorec to do a scan on the raw disk to retrieve its contents).
At the end of the day, what you should *never* do is mess around with a filesystem that was not prior to hibernating. Or if you do, make sure that it does not exist for the kernel (whichever you're using -- Linux, or Windows or anything else) to play with when it resumes. This may not apply to filesystems which have a journal, but then again I have no idea and have no wish to try my luck again. Hence, I do not believe this has anything to do with the file cache. -- Kind regards, Chow Loong Jin (GPG: 0x8F02A411) Ubuntu Contributing Developer -- Slow swapin speeds after resume from disk https://bugs.launchpad.net/bugs/329199 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
