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.
Thanks,
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:You have a known good version, a known bad version and a
> Hi,
>
> I am facing issues in XFS for a simple test case.
> *Target:* ARM
> *Kernel version:* 2.6.35.9
>
> *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.
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?
Cheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
