public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] Fix inode reclaim problems (hopefully)
Date: Thu, 7 Jan 2010 21:49:23 +1100	[thread overview]
Message-ID: <20100107104923.GZ13802@discord.disaster> (raw)
In-Reply-To: <1262819125-27083-1-git-send-email-david@fromorbit.com>

On Thu, Jan 07, 2010 at 10:05:23AM +1100, Dave Chinner wrote:
> These two patches seem to fix the inode reclaim issues I've been
> able to reproduce lately. The changes are still running xfsqa in a
> loop to confirm this, but the directory/small file stress test I've
> been running to trigger the problem has run for 10 hours with these
> fixes instead of dying after 20-30 minutes.

Still running xfsqa 11 hours later without any problem, so it looks
like this series fixes the problem I was seeing. Score another win
for the new tracing code :)

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

      parent reply	other threads:[~2010-01-07 10:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 23:05 [PATCH 0/2] Fix inode reclaim problems (hopefully) Dave Chinner
2010-01-06 23:05 ` [PATCH 1/2] xfs: reclaim inodes under a write lock Dave Chinner
2010-01-08 10:20   ` Christoph Hellwig
2010-01-06 23:05 ` [PATCH 2/2] xfs: reclaim all inodes by background tree walks Dave Chinner
2010-01-08 10:24   ` Christoph Hellwig
2010-01-08 10:43     ` Dave Chinner
2010-01-07 10:49 ` Dave Chinner [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=20100107104923.GZ13802@discord.disaster \
    --to=david@fromorbit.com \
    --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