[Top] [All Lists]

[XFS updates] XFS development tree branch, for-linus, updated. v2.6.34-2

To: xfs@xxxxxxxxxxx
Subject: [XFS updates] XFS development tree branch, for-linus, updated. v2.6.34-20373-g081003f
From: xfs@xxxxxxxxxxx
Date: Wed, 6 Oct 2010 22:56:21 -0500
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "XFS development tree".

The branch, for-linus has been updated
  discards  debd8351de1069838f8d60557e2215e69c785ed3 (commit)
  081003f xfs: properly account for reclaimed inodes
      from  debd8351de1069838f8d60557e2215e69c785ed3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 081003fff467ea0e727f66d5d435b4f473a789b3
Author: Johannes Weiner <hannes@xxxxxxxxxxx>
Date:   Fri Oct 1 07:43:54 2010 +0000

    xfs: properly account for reclaimed inodes
    When marking an inode reclaimable, a per-AG counter is increased, the
    inode is tagged reclaimable in its per-AG tree, and, when this is the
    first reclaimable inode in the AG, the AG entry in the per-mount tree
    is also tagged.
    When an inode is finally reclaimed, however, it is only deleted from
    the per-AG tree.  Neither the counter is decreased, nor is the parent
    tree's AG entry untagged properly.
    Since the tags in the per-mount tree are not cleared, the inode
    shrinker iterates over all AGs that have had reclaimable inodes at one
    point in time.
    The counters on the other hand signal an increasing amount of slab
    objects to reclaim.  Since "70e60ce xfs: convert inode shrinker to
    per-filesystem context" this is not a real issue anymore because the
    shrinker bails out after one iteration.
    But the problem was observable on a machine running v2.6.34, where the
    reclaimable work increased and each process going into direct reclaim
    eventually got stuck on the xfs inode shrinking path, trying to scan
    several million objects.
    Fix this by properly unwinding the reclaimable-state tracking of an
    inode when it is reclaimed.
    Signed-off-by: Johannes Weiner <hannes@xxxxxxxxxxx>
    Cc: stable@xxxxxxxxxx
    Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>


Summary of changes:

XFS development tree

<Prev in Thread] Current Thread [Next in Thread>
  • [XFS updates] XFS development tree branch, for-linus, updated. v2.6.34-20373-g081003f, xfs <=