<div>I am not able to reproduce the same behaviour on 2.6.30.9, had it been on all versions - this can safely be termed as behaviour. But from 2.6.31 onwards this is very much reproducable, especially the change in behaviour of writing to disk.</div>
<div>I will try more things and update if I can find anything new in this.</div>
<div> </div>
<div>Thanks,</div>
<div>Amit Sahrawat<br><br></div>
<div class="gmail_quote">On Thu, Dec 2, 2010 at 9:43 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, Dec 02, 2010 at 09:10:08AM +0530, Amit Sahrawat wrote:<br>> While the copy operation is in progress, simply unplug the usb device and<br>> then replug.<br><br></div>That's pretty much a guaranteed recipe for data and filesystem<br>
corruption regardless of the filesystem you are using. Even if you<br>are lucky enough that there was is no IO being issued while the<br>device is unplugged, what guarantee is there that the device even<br>comes back with the same device name? Further, if the device is usb<br>
powered, there is no guarantee that the drive caches were<br>flushed correctly before the unplug so random log and metadata<br>corruptions are definitely possible.<br>
<div>
<div></div>
<div class="h5"><br>Cheers,<br><br>Dave.<br>--<br>Dave Chinner<br><a href="mailto:david@fromorbit.com">david@fromorbit.com</a><br></div></div></blockquote></div><br>