[Top] [All Lists]

Re: XFS - issues with writes using sync

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: XFS - issues with writes using sync
From: Amit Sahrawat <amit.sahrawat83@xxxxxxxxx>
Date: Thu, 20 Jan 2011 11:37:44 +0530
Cc: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pIYWnhyrnFsa4odN4aeMhyzi1adIVa4TWhQUyXDItp8=; b=a14jcGOIdsrHGctXJqS/u/CUZ4VmmYc+ERxOu/cWlZq6d8dKUgEXpRtC/aNiL6syFF bz1kk9ixJyl/hFqyjUR6oDQb+R7O4sdIrKfY+1WZpHMNnEL4SsgaF070GWSxyssGeS9k kYvLGMHv9bVRy96pqHRMwNWOQFSimvacEPqv4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=r6+k3HnZlLLNdLZVlzL48KnsHOmxrCfeMHJV4KyJrECsAoZ+tBsxQFIJ6WngQYKDDo FsiTATKteSgnNyptdcOzQvE05FiXXPhCf42VNK7lYZNvlHqcy5zCrUOKIdyl1E4GzFUm /NIFWojilYA78WST/A/lnXWl24E3N8+Za1sos=
In-reply-to: <20110120051720.GR16267@dastard>
References: <AANLkTin22efc0cHSmM+2rNQpE2aJoobQCnMwbNUjw617@xxxxxxxxxxxxxx> <20110120051720.GR16267@dastard>
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.

Amit Sahrawat
On Thu, Jan 20, 2011 at 10:47 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
On Thu, Jan 20, 2011 at 10:34:30AM +0530, Amit Sahrawat wrote:
> Hi,
> I am facing issues in XFS for a simple test case.
> *Target:* ARM
> *Kernel version:*
> *Test case:*
> mkfs.xfs -f /dev/sda2
> mount -t xfs /dev/sda2 /mnt/usb/sda2
> (Run script - trying to fragment the XFS formatted partition)
> #!/bin/sh
> index=0
> while [ "$?" == 0 ]
> do
> index=$((index+1))
> sync
> cp /mnt/usb/sda1/setupfile /mnt/usb/sda2/setupfile.$index
> done
> Partition Size on which files are being created - 1GB(I need to fragment
> this first to run other cases)
> Size of *'setupfile'*  - 16K
> There used be no such issues till *2.6.34*(last XFS version where we tried
> to create setup). There is no reset involved this time, just simple running
> the script caused this issue.

You have a known good version, a known bad version and a
reproducable test case. i.e. everything you need to run a git bisect
and find the commit introduced the regression. Can you do this and
tell us what that commit is?


Dave Chinner

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