From: Theodore Ts'o <tytso@mit.edu>
To: Imran Chaudhry <ichaudhry@gmail.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
Akinobu Mita <akinobu.mita@gmail.com>,
679830@bugs.debian.org, linux-ext4@vger.kernel.org
Subject: Re: Bug#679830: linux-image-2.6.32-5-686: Kernel bug observed in syslog when performing an rsync operation.
Date: Sun, 22 Jul 2012 19:33:53 -0400 [thread overview]
Message-ID: <20120722233353.GC9958@thunk.org> (raw)
In-Reply-To: <CABpWkk_4=E=GMY5MhyD9ysyUSr=3F=aCqAxQ_07g5s9N8KQhjg@mail.gmail.com>
On Sun, Jul 22, 2012 at 11:26:18AM +0100, Imran Chaudhry wrote:
>
> Thanks for your reply Ben.
>
> As an aside, from what kernel version would you recommend use of ext4 in?
>
> Maybe I should use (tried and rusted) ext3 for my backup devices. I
> mentioned this problem in my local LUG and a couple of people reported
> similar problems with ext4.
There were a lot of important bug fixes were integrated in the oh,
2.6.35 or 2.6.36. Unfortunately, porting the necessary ext4 patches
to 2.6.32 was very difficult, since some of the patches in question
had prerequisites that involved fairly massive changes to the quota
subsystem.
An enterprise distro such as Red Hat could make the backports work,
but it wasn't easy, and Red Hat by policy doesn't release its broken
out patches, so it's hard for Oracle (and Debian) to profit by the
yeoman work done by Eric Sandeen. (Note, by the way, not his fault;
blame Red Hat management.)
As a result, I would strongly recommend that people use a more modern
3.x kernel.
Since Debian Wheezy will be using a 3.2-based kernel, this problem
will be addressed for the Debian stable users (hopefully!) soon.
Regards,
- Ted
prev parent reply other threads:[~2012-07-22 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120701221420.1784.81013.reportbug@altair.ejectdisc.net>
2012-07-22 4:49 ` Bug#679830: linux-image-2.6.32-5-686: Kernel bug observed in syslog when performing an rsync operation Ben Hutchings
2012-07-22 8:21 ` Akinobu Mita
2012-07-22 10:26 ` Imran Chaudhry
2012-07-22 23:33 ` Theodore Ts'o [this message]
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=20120722233353.GC9958@thunk.org \
--to=tytso@mit.edu \
--cc=679830@bugs.debian.org \
--cc=akinobu.mita@gmail.com \
--cc=ben@decadent.org.uk \
--cc=ichaudhry@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).