From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12151] Unexplained fsck errors on a ext4 filesystem
Date: Sat, 2 May 2009 16:29:30 GMT [thread overview]
Message-ID: <200905021629.n42GTU6W031805@demeter.kernel.org> (raw)
In-Reply-To: <bug-12151-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12151
--- Comment #10 from Nathan Grennan <kernel-bugzilla@cygnusx-1.org> 2009-05-02 16:29:29 ---
Here is my basic experience with ext4. I had two basic problems.
One was where the system would just go off into a hang. The other was this
issue. This issue went away when I went with a 2.6.28+ kernel. Backporting
patches didn't work for me. I say this because at the time you guys were
telling me there were no new patches, but I would have issue with 2.6.27
kernels, but not 2.6.28 kernels. Later cebbert said there was something nasty
in 2.6.28.1 kernels, so I upgraded to 2.6.29. I have had zero issues with ext4
since upgrading to 2.6.29.
I just looked through my irc logs, and found the errors that I think caused
this problem. Sandeen, I have mentioned these to you before. How I think it
would go would be I would get one of these errors, the system would continue,
because that is the crazy default. Then a few days later, I having not noticed
these errors, would reboot the system, and receive the fsck issue above. From
what I remember reading this issue was fixed.
Feb 16 12:03:19 proton kernel: EXT4-fs error (device md3):
ext4_mb_generate_buddy: EXT4-fs: group
EXT4-fs error (device md3): mb_free_blocks: double-free of inode 0's block
321550248(bit 30632 in group 9812)
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-05-02 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 21:38 [Bug 12151] New: Unexplained fsck errors on a ext4 filesystem bugme-daemon
2008-12-11 2:33 ` [Bug 12151] " bugme-daemon
2009-01-18 2:24 ` bugme-daemon
2009-01-18 21:30 ` bugme-daemon
2009-03-04 5:41 ` bugme-daemon
2009-03-04 5:43 ` bugme-daemon
2009-04-27 13:40 ` bugzilla-daemon
2009-04-30 9:10 ` bugzilla-daemon
2009-04-30 20:56 ` bugzilla-daemon
2009-05-01 13:52 ` bugzilla-daemon
2009-05-01 15:19 ` bugzilla-daemon
2009-05-02 16:29 ` bugzilla-daemon [this message]
2009-05-02 20:24 ` bugzilla-daemon
2009-05-02 22:14 ` 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=200905021629.n42GTU6W031805@demeter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.