xfs
[Top] [All Lists]

xfstests 065 failures

To: dchinner@xxxxxxxxxx
Subject: xfstests 065 failures
From: Alex Elder <aelder@xxxxxxx>
Date: Wed, 01 Dec 2010 14:29:39 -0600
Cc: Bill Kendall <wkendall@xxxxxxx>, XFS Mailing List <xfs@xxxxxxxxxxx>
Reply-to: aelder@xxxxxxx
Dave, you were asking on IRC about test 065 failures.
I asked Bill Kendall about it and he bisected to find
that the commit below seems to be where the problems
started.  I believe the problem is that one of the
times is not updated properly when renaming the file
"addedfile4".  Here are the commands that might affect
that file in test 065:

        mv addeddir4/addedfile5 addeddir4/addedfile4
        mv addeddir4 addeddir6

I glanced at the commit and saw nothing obviously
wrong, but at the moment I can't really dig into
it any deeper so I thought I'd report what Bill
found so others could look.

                                        -Alex

>From dcd79a1423f64ee0184629874805c3ac40f3a2c5 Mon Sep 17 00:00:00 2001
From: Dave Chinner <dchinner@xxxxxxxxxx>
Date: Tue, 28 Sep 2010 12:27:25 +1000
Subject: [PATCH] xfs: don't use vfs writeback for pure metadata
modifications

Under heavy multi-way parallel create workloads, the VFS struggles
to write back all the inodes that have been changed in age order.
The bdi flusher thread becomes CPU bound, spending 85% of it's time
in the VFS code, mostly traversing the superblock dirty inode list
to separate dirty inodes old enough to flush.

We already keep an index of all metadata changes in age order - in
the AIL - and continued log pressure will do age ordered writeback
without any extra overhead at all. If there is no pressure on the
log, the xfssyncd will periodically write back metadata in ascending
disk address offset order so will be very efficient.

Hence we can stop marking VFS inodes dirty during transaction commit
or when changing timestamps during transactions. This will keep the
inodes in the superblock dirty list to those containing data or
unlogged metadata changes.

However, the timstamp changes are slightly more complex than this -
there are a couple of places that do unlogged updates of the
timestamps, and the VFS need to be informed of these. Hence add a
new function xfs_trans_ichgtime() for transactional changes,
and leave xfs_ichgtime() for the non-transactional changes.

Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx>
Reviewed-by: Alex Elder <aelder@xxxxxxx>
Reviewed-by: Christoph Hellwig <hch@xxxxxx>


<Prev in Thread] Current Thread [Next in Thread>