<div>yes, thats the only approach at the moment which can help. I am doubting the changes related with the disk commit, but I am not sure.</div>
<div> </div>
<div>Thanks,</div>
<div>Amit Sahrawat<br><br></div>
<div class="gmail_quote">On Thu, Dec 2, 2010 at 9:26 AM, Eric Sandeen <span dir="ltr"><<a href="mailto:sandeen@sandeen.net">sandeen@sandeen.net</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 12/1/10 9:40 PM, Amit Sahrawat wrote:<br>> While the copy operation is in progress, simply unplug the usb device and then replug.<br><br></div>that's not a simple copy operation either ;)<br>
<div class="im"><br>> The issue can be seen from XFS (2.6.31) onwards, I am trying to figure out the changes between 2.6.30.9 and 2.6.31.<br><br></div>If you have a regression, perhaps you can do:<br><br># git bisect start v2.6.31 v2.6.30 fs/xfs<br>
<br>and methodically test the changes in between.<br><font color="#888888"><br>-Eric<br></font>
<div class="im"><br>> One thing I noticed is - there is difference in speed for 2 versions - in case of 2.6.30.9 if I remove the USB within '5' seconds - I can see the file being created at the destination and some data written, while in case of 2.6.31(onwards), it takes around 20 seconds to get some data to disk.<br>
> I am using MIPS at the moment with VIPT(fixes included)<br>><br>> Please let me know if this information is useful.<br>><br>> Thanks,<br>> Amit Sahrawat<br></div>
<div>
<div></div>
<div class="h5">> On Wed, Dec 1, 2010 at 8:25 PM, Eric Sandeen <<a href="mailto:sandeen@sandeen.net">sandeen@sandeen.net</a> <mailto:<a href="mailto:sandeen@sandeen.net">sandeen@sandeen.net</a>>> wrote:<br>
><br>> On 12/1/10 1:14 AM, Amit Sahrawat wrote:<br>> > Dear Member,<br>> ><br>> > I am getting following corruption on XFS formatted disk during a simple copy operation:<br>> > sd 9:0:0:0: Attached scsi removable disk sdc<br>
> > sd 9:0:0:0: Attached scsi generic sg2 type 0<br>> > XFS mounting filesystem sdc2<br>> > Starting XFS recovery on filesystem: sdc2 (logdev: internal)<br>> > XFS: xlog_recover_process_data: bad transaction<br>
> > XFS: log mount/recovery failed: error 5<br>> > XFS: log mount failed<br>><br>> hm, that's not a simple copy operation, that is a mount failing;<br>> your log appears to be corrupted.<br>
><br>> offhand I'm going to blame it on having a write cache enabled<br>> on your drive, and having barriers either off, or not working<br>> properly.<br>><br>> -Eric<br>><br>><br>
<br></div></div></blockquote></div><br>