XFS file system corruption(Return Bad Transaction) kernel - 2.6.34

[Amit Sahrawat]

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.
I will try more things and update if I can find anything new in this.

Thanks,
Amit Sahrawat

On Thu, Dec 2, 2010 at 9:43 AM, Dave Chinner <david at fromorbit.com> wrote:

> On Thu, Dec 02, 2010 at 09:10:08AM +0530, Amit Sahrawat wrote:
> > While the copy operation is in progress, simply unplug the usb device and
> > then replug.
>
> That's pretty much a guaranteed recipe for data and filesystem
> corruption regardless of the filesystem you are using. Even if you
> are lucky enough that there was is no IO being issued while the
> device is unplugged, what guarantee is there that the device even
> comes back with the same device name? Further, if the device is usb
> powered, there is no guarantee that the drive caches were
> flushed correctly before the unplug so random log and metadata
> corruptions are definitely possible.
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david at fromorbit.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20101202/db66a616/attachment.htm>