[All releases] Suspend/Resume with rootfs on USB, causes filesystem corruptions and kernel panic on mount attempt, leaving system unbootable with data lost.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Fedora) |
New
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Incomplete
|
Medium
|
Unassigned |
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/
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/
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-
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).
description: | updated |
description: | updated |
summary: |
- Terminated suspend causes ext4 corruptions which crashes kernel on mount - attempt + Suspending with rootfs (mainly ext4) on USB, cause corruption which + crashes kernel on mount attempt |
summary: |
- Suspending with rootfs (mainly ext4) on USB, cause corruption which - crashes kernel on mount attempt + [All releases] Suspending with rootfs (mainly ext4) on USB, cause silent + corruptions which panics kernel on mount attempt. Making system + unbootbale |
summary: |
[All releases] Suspending with rootfs (mainly ext4) on USB, cause silent corruptions which panics kernel on mount attempt. Making system - unbootbale + unbootable |
summary: |
[All releases] Suspending with rootfs (mainly ext4) on USB, cause silent corruptions which panics kernel on mount attempt. Making system - unbootable + unbootable. |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
description: | updated |
tags: | removed: needs-kernel-logs needs-upstream-testing |
summary: |
- [All releases] Suspending with rootfs on USB, causes silent corruptions, - kernel panic on mount attempt, data loss and leaving system unbootable. + [All releases] Suspend/Resume with rootfs on USB, causes filesystem + corruptions and kernel panic on mount attempt, leaving system unbootable + with data lost. |
description: | updated |
tags: | added: maverick |
Hi Eugene,
Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http:// cdimage. ubuntu. com/daily/ current/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command from a Terminal (Applications- >Accessories- >Terminal) it will automatically gather and attach updated debug information to this report.
apport-collect -p linux 706795
Also, please be sure to take a look at https:/ /wiki.ubuntu. com/DebuggingKe rnelSuspendHibe rnateResume . If you can provide any additional information outlined there it would be much appreciated.
Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. Thanks in advance.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]