This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/706795
Title:
[All releases] Suspend/Resume with rootfs on USB, causes filesystem
corruptions and kernel panic on mount attempt, leaving system
unbootable with data lost.
Status in linux package in Ubuntu:
Won't Fix
Status in linux package in Fedora:
New
Bug description:
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).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/706795/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
