Bug 772174
Summary: | kernel 3.2 hibernation and ext4 fs write problem | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jacek Pawlyta <cunio> |
Component: | kernel | Assignee: | Eric Sandeen <esandeen> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-02-17 12:36:27 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jacek Pawlyta
2012-01-06 09:54:37 UTC
Eric, this is clearly the unlock_new_inode bug but it's on the final 3.2 release build in rawhide. I'll leave it to you to dupe the bug if you want in case 3.2 makes this somehow more compelling/easier to debug. (I'm intentionally ignoring the P taint here) Josh, the P is here because I'm not able to use brcmsmac driver due to the bug: #771477 After some research I have found that it has something to do with sandbox, I switched off the sandbox as suggested here: https://bugzilla.redhat.com/show_bug.cgi?id=742708 rebooted and it seems for now that the hibernation works without corruption of the ext4 fs. Funky, but good to know; ok, let me try to test that particular setup. kernel 3.2.1-2 + sandbox off + resume from hibernation = [ 842.202641] EXT4-fs error (device dm-1) in ext4_new_inode:941: IO failure [ 842.378472] EXT4-fs error (device dm-1) in ext4_new_inode:941: IO failure [ 851.928284] EXT4-fs error (device dm-1) in ext4_new_inode:941: IO failure kernel 3.2.0-2 + sandbox off = OK The IO failure message is due to new & improved error handling - at least now it doesn't WARN_ON and backtrace :) I've been unable thus far to repro even w/ sandbox turned on. Argh! kernel 3.2.6-4.fc16.x86_64 + sandbox off + hibernation = EXT4-fs error (device dm-1) in ext4_new_inode:941: IO failure The same result with sandbox on :( The same results with previous kernels 3.2 My system: http://www.smolts.org/client/show/pub_503fa95d-8ef3-46f5-b1ae-014b47bd254d *** This bug has been marked as a duplicate of bug 744275 *** |