> Could you make sure that the filesystem(REISERFS) on the external device > has been destroyed? If only the single file is affected, it should not be a > big > deal.
I'm sorry, but this is unacceptable. It is not correct for even a single file to be affected by this problem. What if it happens to be a very important file? When it comes to filesystem integrity, it's either fully correct or it isn't - there is no "partial credit" here. The workaround can be done entirely from userspace, without having to wait for linux-pm guys to sort their stuff out. Back when I ran a gentoo box, I had a suspend script with a simple 5 lines of shell code which tried to unmount external devices, and did not initiate suspend unless this operation completed. Sure, the problem would still occur if you directly echo mem > /sys/power/state, but at least clicking 'Suspend' from the UI would try to do the right thing first, and fail to suspend if unmounting was unsuccessful. Maybe I will just go back to that script on this system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883748 Title: Suspend/resume corrupts external data storage devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/883748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
