<div>Hi,</div>
<div> </div>
<div>I will try to find out the cause for this.</div>
<div>Meanwhile, just a small request/suggestion - in the past this type of testcases have helped us in finding many problems in XFS. </div>
<div>Can something like this be added to xfstests? This might help. </div>
<div><br>Thanks,</div>
<div>Amit Sahrawat<br></div>
<div class="gmail_quote">On Thu, Jan 20, 2011 at 10:47 AM, Dave Chinner <span dir="ltr"><<a href="mailto:david@fromorbit.com">david@fromorbit.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">On Thu, Jan 20, 2011 at 10:34:30AM +0530, Amit Sahrawat wrote:<br>> Hi,<br>><br>> I am facing issues in XFS for a simple test case.<br>> *Target:* ARM<br>> *Kernel version:* 2.6.35.9<br>><br>
> *Test case:*<br>> mkfs.xfs -f /dev/sda2<br>> mount -t xfs /dev/sda2 /mnt/usb/sda2<br>> (Run script - trying to fragment the XFS formatted partition)<br>> #!/bin/sh<br>> index=0<br>> while [ "$?" == 0 ]<br>
> do<br>> index=$((index+1))<br>> sync<br>> cp /mnt/usb/sda1/setupfile /mnt/usb/sda2/setupfile.$index<br>> done<br>><br>> Partition Size on which files are being created - 1GB(I need to fragment<br>> this first to run other cases)<br>
> Size of *'setupfile'* - 16K<br>><br>> There used be no such issues till *2.6.34*(last XFS version where we tried<br>> to create setup). There is no reset involved this time, just simple running<br>> the script caused this issue.<br>
<br></div>You have a known good version, a known bad version and a<br>reproducable test case. i.e. everything you need to run a git bisect<br>and find the commit introduced the regression. Can you do this and<br>tell us what that commit is?<br>
<br>Cheers,<br><br>Dave.<br><font color="#888888">--<br>Dave Chinner<br><a href="mailto:david@fromorbit.com">david@fromorbit.com</a><br></font></blockquote></div><br>