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.
This ticket is specifically about the data of running programs. That cannot be discarded. The hibernation mechanism forces it all out from RAM into swap. Since the programs were using that data (which is why it was in RAM) they end up sucking it back in but using page faults which is extremely inefficient. TuxOnIce saves file caches (dangerous) but also saves the data and compresses it. On resume it is all brought back into memory at once and so the programs can continue running, Any mechanism that puts back into RAM what was already there before hibernating would work well. Additionally the page faults cause random disk access which is very slow. If the data was brought back then the disk would be free for repopulating the file cache. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
