Hide Forgot
+++ This bug was initially created as a clone of Bug #680505 +++ Suspend of root filesystem on USB, causes FS corruptions which crashes kernel on mount attempt and making systen unbootable. Affects (at least) RedHat6.0+, Fedora13+ and Ubuntu10+. Reconstruction (Full): --------------- a) Install any RedHat/Fedora/Ubuntu release on USB drive. b) Boot into user session c) Suspend d) Resume e) Repeat c,d (up to 4 times) until kernel informs about filesystem corruption. f) Reset the system -> Observe system inability to boot and kernel panic due to corrupted FS. Reconstruction (Short): --------------- a) Install any RedHat/Fedora/Ubuntu release on USB drive. b) Boot into user session c) Suspend d) Hard reset the system (Before performing resume) -> Observe system inability to boot and kernel panic due to corrupted FS. Actually report describes two severe issues: -------------------------------------------- a) FS corruption during suspend/resume b) Kernel panic when trying to mount affected FS. Facts: ------ *) Happens on systems with bootdevice on USB. *) When system returns from suspend, there is a chance of ~25% for rootfs on USB to be remounted as readonly. Due to short inability to read from USB device (device settle delay required) *) Attempt to start affected FS will result an useless initramfs prompt without ability to solve the issue locally. *) To fix the issue additional Linux system required (with auto-mount de-activated!). *) An attempt to mount affected EXT4 will results a crashed provided below. Corruptions are silent, FS marked as clean, that's what causes Kernel panic when it tries to mount corrupted FS marked as clean. *) Issue caused probably by partially synced disk cache. *) All tested Kernels affected (Lucid, Maverick, Natty, Natty-Mainline-Daily, Fedora14, Redhat6). *) Validated with: Mainline, Lucid, Maverick, Natty, Fedora14 and RedHat6. *) Kernels above 2.6.38 manages to mark FS as dirty during failed mount attempt, so virtually corruption got fixed after 2 reboots but loss is there. *) Bug affects all filesystems, but severe for EXT4(data loss while fixable with another system without automount) and BTRFS (unfixable due to failed mounttime fixes and there is no way to fix manually). --- Additional comment from eugenesan on 2011-02-25 13:24:07 EST --- Created attachment 481056 [details] suspend resume cycle with pm-trace and USB debug --- Additional comment from eugenesan on 2011-02-25 13:24:51 EST --- Created attachment 481058 [details] reconstruction script
I can almost reproduce this. I have a system on a USB drive on Fedora 15. It is impossible for me as well to resume from suspend but this as not corrupted my root file system so far.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping