From: Alex Elder <aelder@sgi.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com, akpm@linux-foundation.org
Subject: [GIT PULL] XFS fix for 2.6.36
Date: Wed, 06 Oct 2010 23:27:48 -0500 [thread overview]
Message-ID: <201010070427.o974RmcC012153@stout.americas.sgi.com> (raw)
I'm hoping this XFS change can make it in to 2.6.36. It fixes a bug
that causes allocation groups to be needlessly scanned for reclaim,
because some reclaim state in XFS is never properly cleared when an
inode gets reclaimed. The result can make filesystems appear to
have an ever-increasing number of reclaimable objects, even if there
is nothing to do.
-Alex
The following changes since commit cb655d0f3d57c23db51b981648e452988c0223f9:
Linux 2.6.36-rc7 (2010-10-06 13:39:52 -0700)
are available in the git repository at:
git://oss.sgi.com/xfs/xfs for-linus
Johannes Weiner (1):
xfs: properly account for reclaimed inodes
fs/xfs/linux-2.6/xfs_sync.c | 19 ++++++++++++++-----
1 files changed, 14 insertions(+), 5 deletions(-)
reply other threads:[~2010-10-07 4:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201010070427.o974RmcC012153@stout.americas.sgi.com \
--to=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®