[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090806170543.GA32511@fieldses.org>
Date: Thu, 6 Aug 2009 13:05:43 -0400
From: "J. Bruce Fields" <bfields@...ldses.org>
To: Sylvain Rochet <gradator@...dator.net>
Cc: Jan Kara <jack@...e.cz>, linux-kernel@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-nfs@...r.kernel.org,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: 2.6.28.9: EXT3/NFS inodes corruption
On Thu, Aug 06, 2009 at 03:15:56PM +0200, Sylvain Rochet wrote:
> Hi,
>
>
> On Wed, Aug 05, 2009 at 12:56:19AM +0200, Jan Kara wrote:
> >
> > Thanks for testing. So you seem to be really stressting the path where
> > creation of new files / directories fails (probably due to group quota).
>
> Yes, there are 29 groups over quota on a total of 4499. Those are mainly
> spammed websites and therefore quite stressed due to the amount of tries
> to add new "data".
>
>
> > I have one idea what could cause your filesystem corruption, although
> > it's a wild guess... Please try attached oneliner.
>
> Running since yesterday.
>
>
> > Also your corruption reminded me that Al Viro has been fixing problems
> > where we could cache one inode twice when a filesystem was mounted over NFS
> > and that could also lead to a filesystem corruption. So I'm adding him to
> > CC just in case he has some idea. BTW Al, what do you think about the
> > problem I describe in the attached patch? I'm not sure if it can cause some
> > real problems but in theory it could...
>
> Should we upgrade NFS clients as well ? (now running 2.6.28.9)
The client version shouldn't matter.
--b.
--
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