xfs
[Top] [All Lists]

Re: XFS - issues with writes using sync

To: Amit Sahrawat <amit.sahrawat83@xxxxxxxxx>
Subject: Re: XFS - issues with writes using sync
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 20 Jan 2011 17:41:37 +1100
Cc: xfs@xxxxxxxxxxx
In-reply-to: <AANLkTik0KUQaRzLeBNR8M=u+ijO6gAZu601zyCp2zmDS@xxxxxxxxxxxxxx>
References: <AANLkTin22efc0cHSmM+2rNQpE2aJoobQCnMwbNUjw617@xxxxxxxxxxxxxx> <20110120051720.GR16267@dastard> <AANLkTik0KUQaRzLeBNR8M=u+ijO6gAZu601zyCp2zmDS@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)
On Thu, Jan 20, 2011 at 11:37:44AM +0530, Amit Sahrawat wrote:
> Hi,
> 
> I will try to find out the cause for this.
> Meanwhile, just a small request/suggestion - in the past this type of
> testcases have helped us in finding many problems in XFS.
> Can something like this be added to xfstests? This might help.

Definitely.  We're always looking for more people to add tests that
expose problems to xfstests. :) We try to keep individual test
runtime to as little as possible - under 5 minutes for the auto
group, under 15s for the quick group, but by the looks of it the
test you are running doesn't take that long to run.

FWIW, there are already tests that cause worst case filesystem
fragmentation as part of their test setup (e.g. test 042) but the
coverage of such issues could definitely be improved. Also, the way
we generate fragmented filesystems - by writing files and then
removing a subset - could be greatly sped up by preallocation and
hole punching. There's no need to write data when we could just use
unwritten extents to do the same thing...

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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