[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2013-08-18 Thread Christopher M. Penalver
** Tags added: bios-outdated-2.30 needs-suspend-logs regression- potential ** Summary changed: - Suspend/resume corrupts external data storage devices + [reiserfs] Suspend/resume corrupts external data storage devices -- You received this bug notification because you are a member of Ubuntu

[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2013-03-11 Thread Nathan Korth
This is still a problem; I've been having issues using an SD card with a netbook that has very little internal memory. After resume, the mount is still there but it doesn't work. In fact, one time it seems to have caused a kernel panic: Mar 9 22:16:09 nkorth-mini kernel: [12594.477903] EXT4-fs

Re: [Bug 883748] Re: Suspend/resume corrupts external data storage devices

2013-03-11 Thread Steve
I don't understand why distributions think it is okay to keep removable devices mounted across suspend. This is just asking for data corruption. I've written some sleep scripts that prevent suspend of unmount could not be done but these are fairly hacked up... On Mar 11, 2013 6:45 AM, Nathan Korth

[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2012-07-31 Thread Steve
I have been working around the problem with a shell script hack that tries to unmount all my known media prior to suspending. Yes, sometimes it kicks me back to the unlock screen without suspending if I left a terminal open somewhere that points to external media, but that's kind of the point (and

[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2012-07-30 Thread Christopher M. Penalver
** Tags added: needs-upstream-testing resume suspend -- 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

[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2011-12-11 Thread Steve
Experienced this once again. Given the severity of the problem, I cannot believe this is not getting immediate attention. The device was not removed or even touched between suspend and resume. The mount point is filled with some half-assed combination of the original drive contents and

[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2011-10-31 Thread Brad Figg
** Changed in: linux (Ubuntu) Status: New = Confirmed -- 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

Re: [Bug 883748] Re: Suspend/resume corrupts external data storage devices

2011-10-31 Thread Ming Lei
Hi, On Sun, Oct 30, 2011 at 11:31 PM, Steve 883...@bugs.launchpad.net wrote: First,  problems can occur because there may be open files on the device when the system is suspended. Due to delays in enumeration, the external device will not immediately be back when the system is resumed. Thus,

[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2011-10-31 Thread Steve
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

Re: [Bug 883748] Re: Suspend/resume corrupts external data storage devices

2011-10-31 Thread Ming Lei
On Tue, Nov 1, 2011 at 2:44 AM, Steve 883...@bugs.launchpad.net wrote: 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

[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2011-10-31 Thread Steve
You may not umount successfully if accesses to the filesystem is pending or ongoing. Yes, that is exactly the point. If you cannot unmount, you cannot and SHOULD NOT suspend. So, if the user clicks Suspend and everything in /media cannot be unmounted, you give an error instead of suspending.

Re: [Bug 883748] Re: Suspend/resume corrupts external data storage devices

2011-10-31 Thread Ming Lei
On Tue, Nov 1, 2011 at 5:55 AM, Steve 883...@bugs.launchpad.net wrote: You may not umount successfully if accesses to the filesystem is pending or ongoing. Yes, that is exactly the point. If you cannot unmount, you cannot and SHOULD NOT suspend. So, if the user clicks Suspend and everything

[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2011-10-31 Thread Steve
It will make user confused if suspend operation is just failed because of a usb mass storage device connected and some directories or files are open, looks like it is a bit stupid, doesn't it? It looks a lot MORE stupid if you allow the suspend to happen, but then destroy the data on the disk.

[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2011-10-30 Thread Steve
-- 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:

[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2011-10-30 Thread Ubuntu QA's Bug Bot
** Package changed: ubuntu = linux (Ubuntu) -- 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

[Bug 883748] Re: Suspend/resume corrupts external data storage devices

2011-10-30 Thread Steve
First, problems can occur because there may be open files on the device when the system is suspended. Due to delays in enumeration, the external device will not immediately be back when the system is resumed. Thus, the effect is that of essentially unplugging the device without unmounting it