mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Sylvain Rochet <gradator@gradator.net>
Cc: Jan Kara <jack@suse.cz>,
	linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-nfs@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: 2.6.28.9: EXT3/NFS inodes corruption
Date: Thu, 6 Aug 2009 13:05:43 -0400	[thread overview]
Message-ID: <20090806170543.GA32511@fieldses.org> (raw)
In-Reply-To: <20090806131555.GA23359@gradator.net>

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.

  reply	other threads:[~2009-08-06 17:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 16:20 Sylvain Rochet
2009-07-16 17:27 ` Jan Kara
2009-07-25 15:17   ` Sylvain Rochet
2009-07-27 15:42     ` Jan Kara
2009-07-28 11:27       ` Sylvain Rochet
2009-07-28 13:52         ` Jan Kara
2009-07-28 16:41           ` Sylvain Rochet
2009-07-28 21:12             ` J. Bruce Fields
2009-08-04 10:50               ` Sylvain Rochet
2009-07-29 12:58             ` Jan Kara
2009-08-04 11:02               ` Sylvain Rochet
2009-08-03 22:29             ` Jan Kara
2009-08-04 11:15               ` Sylvain Rochet
2009-08-04 22:56                 ` Jan Kara
2009-08-06 13:15                   ` Sylvain Rochet
2009-08-06 17:05                     ` J. Bruce Fields [this message]
2009-08-12 22:34                     ` Jan Kara
2009-08-20 17:19                       ` Sylvain Rochet
2009-08-21  0:00                         ` Simon Kirby
2009-08-21 10:51                           ` Sylvain Rochet
     [not found] <ct4xS-63o-27@gated-at.bofh.it>
2009-07-28 16:40 ` Daniel J Blueman
2009-07-28 16:45   ` Sylvain Rochet
2009-08-21 11:05     ` Daniel J Blueman
2009-08-21 14:32       ` Sylvain Rochet

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=20090806170543.GA32511@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=gradator@gradator.net \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

Powered by JetHome