xfs
[Top] [All Lists]

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

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: XFS file system corruption(Return Bad Transaction) kernel - 2.6.34
From: Amit Sahrawat <amit.sahrawat83@xxxxxxxxx>
Date: Thu, 2 Dec 2010 10:08:49 +0530
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs@xxxxxxxxxxx, sandeen-xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=7giLKChMisuw7WvE9okr4pVIv3jUNUrYns1QzEBQGUI=; b=p7JWWetSO9JHzm0ughghPpre3ZLJONc0ecPtSJmNCY8Xcgs7YovVfShowSf94N+bFA vrlX0wVNK41B7nTGCf4itbBPB13C077BEqVp7T+QY1SG1kaXv6944QSkA/wkM5OYB477 1GU1A9VFzvoRwMF47CGoM/bnMDAimHohMYAHo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=dMjeilD2oq5U1Bui0QDvUPaW6QEBoFh1PvXb7QtrQtstI8TwKn6HKnTBRqqvODfhJr 6A28sAmAMA8iFNcQ7ifgtKmABROpnjbHf0/ZLeJTrj/PD+zWe7GUlNZ8Y+5gbeCCX6wM 6wwpZpL31XgmDX63qtCG1GMpawMefR3kyIAWY=
In-reply-to: <20101202041312.GX16922@dastard>
References: <AANLkTikzCpQ1j9uWGSTY9TEguVDvAB5AVYtbDtdePFci@xxxxxxxxxxxxxx> <4CF661C7.2020103@xxxxxxxxxxx> <AANLkTimiST8VNVsV49mniKLBudSxFj+O883Mwwe7ucac@xxxxxxxxxxxxxx> <20101202041312.GX16922@dastard>
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@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>