From: Ted Ts'o <tytso@mit.edu>
To: Micah Anderson <micah@riseup.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 corruption
Date: Mon, 6 Jun 2011 00:19:50 -0400 [thread overview]
Message-ID: <20110606041950.GH7180@thunk.org> (raw)
In-Reply-To: <87pqmrobix.fsf@algae.riseup.net>
On Sun, Jun 05, 2011 at 11:59:34PM -0400, Micah Anderson wrote:
>
> I previously wrote about a recent conversion from ext3 to ext4 (on
> Debian Squeeze), which went well. However, I seem to be having problems
> with the ext4 filesystem.
Are you using the 2.6.32 kernel (the Debian squeeze default)? Try
updating to 2.6.39.1, and see if that stablizes things. There have
been a huge number of bug fixes since 2.6.32, and no one has been
really backporting patches to such an ancient kernel. This is one of
the ways in which Debian Obsolete^H^H^H^H^H^H^H^H Stable can be
somewhat of a disadvantage. Unlike the RHEL kernels, no one is
backporting ext4 bugfixes to older Debian stable kernels, and ext4 was
still getting a lot of bug fixes in the 2.6.32 days.
That being said, you're seeing some pretty severe inode *and* block
allocation bitmap problems, and that doesn't sound like anything I
remember even back in the 2.6.32 days. It does make me wonder about
the stability of the hardware and of the software raid code...
- Ted
next prev parent reply other threads:[~2011-06-06 4:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 3:59 ext4 corruption Micah Anderson
2011-06-06 4:19 ` Ted Ts'o [this message]
2011-06-06 17:11 ` micah anderson
-- strict thread matches above, loose matches on Subject: below --
2011-02-26 10:16 Bill Huey (hui)
2011-02-26 11:10 ` Theodore Tso
2011-02-26 11:13 ` Bill Huey (hui)
2011-02-26 11:16 ` Bill Huey (hui)
2011-02-28 4:43 ` Ted Ts'o
2011-02-28 20:18 ` Bill Huey (hui)
2011-02-28 20:30 ` Bill Huey (hui)
2011-02-28 22:55 ` Ted Ts'o
2011-02-28 23:45 ` Bill Huey (hui)
2011-02-28 15:01 ` Eric Sandeen
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=20110606041950.GH7180@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=micah@riseup.net \
/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;
as well as URLs for NNTP newsgroup(s).