[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100826102535.C327.61FB500B@jp.fujitsu.com>
Date: Thu, 26 Aug 2010 10:25:36 +0900
From: Masayoshi MIZUMA <m.mizuma@...fujitsu.com>
To: Andreas Dilger <adilger.kernel@...ger.ca>,
"Ted Ts'o" <tytso@....edu>
Cc: Jan Kara <jack@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>,
linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] [RESEND] ext3: set i_extra_isize of 11th inode
On Wed, 25 Aug 2010 18:55:49 -0600
Andreas Dilger <adilger@...ger.ca> wrote:
> On 2010-08-25, at 18:36, Ted Ts'o wrote:
> > On Wed, Aug 25, 2010 at 05:39:11PM -0600, Andreas Dilger wrote:
> >>
> >> The fix to e2fsck for this issue has been around for a long time,
> >> AFAIK. It was only needed in the kernel while the broken mke2fs was
> >> in wide use, and before a fixed e2fsck was available.
> >
> > The mke2fs in question was fixed in e2fsprogs 1.37, over five years
> > ago. Mizuma-san, why are you using such an __ancient__ mke2fs? It
> > would seem that instead of fixing the kernel, the better thing to do
> > is to fix your version of e2fsprogs.
>
> I think you are missing the point. I don't think it matters which mke2fs is in use. The problem is that ext3_iget() has a workaround for this 5-year-old mke2fs bug that is actively causing a loss of xattr data if lost+found is reallocated.
I used e2fsprogs 1.41. I think this problem isn't mke2fs's problem,
so I agree with Andreas.
Thanks,
Masayoshi
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists