public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [RFC] Delayed logging
Date: Tue, 16 Mar 2010 12:20:51 +1100	[thread overview]
Message-ID: <20100316012051.GD12369@dastard> (raw)
In-Reply-To: <20100315180841.GA21975@infradead.org>

On Mon, Mar 15, 2010 at 02:08:41PM -0400, Christoph Hellwig wrote:
> On Mon, Mar 15, 2010 at 03:30:00PM +1100, Dave Chinner wrote:
> > 	- occasional recovery failure with recovery reading an inode
> > 	  buffer that does not contain inodes. Cause unknown, tends
> > 	  to be reproduced by xfsqa test 121 semi-reliably. Needs
> > 	  further analysis and fixing. May already be fixed with a
> > 	  recent fix to commit record synchronisation.
> 
> I just saw a corrupted inode buffer during log recovery in 087, even
> without the delaylog mount option.  It's however not easily
> reproducible.

Yeah, that's the sort of thing I'm seeing 087, 110 (IIRC) and 121
are the tests that I've been seeing occasional, random failures like
this. I hadn't noticed it without the delaylog option, so I'll see
if I can get that to occur as well...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-03-16  1:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15  4:30 [RFC] Delayed logging Dave Chinner
2010-03-15 16:01 ` Christoph Hellwig
2010-03-15 16:33   ` Christoph Hellwig
2010-03-16  1:06     ` Dave Chinner
2010-03-15 16:08 ` Christoph Hellwig
2010-03-16  1:14   ` Dave Chinner
2010-03-15 16:38 ` Christoph Hellwig
2010-03-16  1:15   ` Dave Chinner
2010-03-15 18:08 ` Christoph Hellwig
2010-03-16  1:20   ` Dave Chinner [this message]
2010-03-31 13:26   ` Dave Chinner

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=20100316012051.GD12369@dastard \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.com \
    /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