From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 16019] New: Resume from hibernate corrupts ext4
Date: Thu, 20 May 2010 22:49:47 GMT [thread overview]
Message-ID: <bug-16019-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=16019
Summary: Resume from hibernate corrupts ext4
Product: Power Management
Version: 2.5
Kernel Version: 2.6.33.4-95
Platform: All
OS/Version: Linux
Tree: Fedora
Status: NEW
Severity: high
Priority: P1
Component: Hibernation/Suspend
AssignedTo: power-management_other@kernel-bugs.osdl.org
ReportedBy: lowe@brown.edu
CC: fs_ext4@kernel-bugs.osdl.org
Regression: No
Overview: System appears to hibernate successfully. Upon resume at first sight
all seems well until one discovers it is no longer possible to write to disk.
Steps to reproduce:
1) Hibernate system to disk. (Note suspend to ram seems to work ok).
2) Resume from disk.
3) System starts up ok, but disk seems to be mounted read only. Sometimes
resume just fails and system auto reboots itself and fixes the ext4 disk
errors.
4) Rebooting seems to fix the disk issues.
Expected result:
Resume from hibernate should work ok.
System info: Fedora 13 kernel 2.6.33.4-95.fc13.x86_64
Dell Latitude D630, 2G ram, 4G swap
Attached log messages from suspend/resume cycle.
First ext4 error is
May 20 06:28:41 trillian kernel: EXT4-fs error (device dm-0):
ext4_mb_generate_buddy: EXT4-fs: group 26: 1161 blocks in bitmap, 1149 in gd
May 20 06:28:41 trillian kernel: JBD: Spotted dirty metadata buffer (dev =
dm-0, blocknr = 0). There's a risk of filesystem corruption in case of system
crash.
then it ends with lots of
May 20 06:50:20 trillian kernel: EXT4-fs error (device dm-0): mb_free_blocks:
double-free of inode 0's block 872631(bit 20663 in group 26)
May 20 06:50:20 trillian kernel: EXT4-fs error (device dm-0): mb_free_blocks:
double-free of inode 0's block 872632(bit 20664 in group 26)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
next reply other threads:[~2010-05-20 22:49 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 22:49 bugzilla-daemon [this message]
2010-05-20 22:55 ` [Bug 16019] Resume from hibernate corrupts ext4 bugzilla-daemon
2010-05-20 23:00 ` bugzilla-daemon
2010-05-20 23:36 ` bugzilla-daemon
2010-05-21 0:11 ` bugzilla-daemon
2010-05-21 10:36 ` bugzilla-daemon
2010-05-21 17:11 ` bugzilla-daemon
2010-05-21 18:00 ` bugzilla-daemon
2010-05-21 18:04 ` bugzilla-daemon
2010-05-21 18:25 ` bugzilla-daemon
2010-05-21 19:59 ` bugzilla-daemon
2010-05-22 0:37 ` bugzilla-daemon
2010-05-22 0:40 ` bugzilla-daemon
2010-05-22 4:34 ` bugzilla-daemon
2010-05-22 17:03 ` bugzilla-daemon
2010-05-22 17:10 ` bugzilla-daemon
2010-05-24 14:59 ` bugzilla-daemon
2010-05-24 17:00 ` bugzilla-daemon
2010-05-28 23:03 ` bugzilla-daemon
2010-06-01 16:02 ` bugzilla-daemon
2010-06-16 3:10 ` bugzilla-daemon
2010-06-17 15:49 ` bugzilla-daemon
2010-06-17 15:51 ` bugzilla-daemon
2010-06-17 16:28 ` bugzilla-daemon
2010-06-17 16:35 ` bugzilla-daemon
2010-06-17 16:47 ` bugzilla-daemon
2010-06-17 19:16 ` bugzilla-daemon
2010-06-17 19:24 ` bugzilla-daemon
2010-06-17 21:37 ` bugzilla-daemon
2010-06-17 21:45 ` bugzilla-daemon
2010-06-17 23:37 ` bugzilla-daemon
2010-06-18 6:32 ` bugzilla-daemon
2010-06-18 9:40 ` bugzilla-daemon
2010-06-18 13:59 ` bugzilla-daemon
2010-06-18 14:39 ` bugzilla-daemon
2010-06-18 14:51 ` bugzilla-daemon
2010-06-18 14:52 ` bugzilla-daemon
2010-07-01 5:04 ` bugzilla-daemon
2010-07-16 21:15 ` bugzilla-daemon
2010-07-27 20:37 ` bugzilla-daemon
2011-01-16 22:34 ` bugzilla-daemon
2011-01-17 18:14 ` bugzilla-daemon
2011-01-30 11:13 ` bugzilla-daemon
2011-02-15 15:31 ` bugzilla-daemon
2011-03-21 15:04 ` bugzilla-daemon
2011-05-25 21:10 ` bugzilla-daemon
2011-05-26 16:32 ` bugzilla-daemon
2012-01-18 2:10 ` bugzilla-daemon
2012-05-24 7:34 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-16019-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox