[Top] [All Lists]

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

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: XFS file system corruption(Return Bad Transaction) kernel - 2.6.34
From: Amit Sahrawat <amit.sahrawat83@xxxxxxxxx>
Date: Thu, 2 Dec 2010 09:10:08 +0530
Cc: xfs@xxxxxxxxxxx, sandeen-xfs@xxxxxxxxxxx, david@xxxxxxxxxxxxx
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=3eN9FK9Or81wtpTdaaWuXhb7tYTYejpWdMFL4SfU184=; b=Ot6PbvfXc/l1zqKbxX+LM5oL7Xgoi7r7KC8FlOG9t9juebnWWbRlUizVSdjiNDr63Y r9Asgaiw6ueQWbG7F7yBxwIXY5SpcXNw1wieA090u/iwUJ6gqzVGa9+pVNkTiYikaq47 15wpf8a5t1rOxdIEaIAQ+4jOvewox+bsYqRc8=
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=sWeGKdIUHbL+7XcpfPssn87LoXu4l0Mr3n8sY5/8ekITIHKVKY/1hoG9Ghx/DnJgoE c0wQ/UeAYaWn7hq6jEqDKy9dNMovvOMeyoPB2bd1xUdpdasifJtCiqW2kc4TtUfufVKJ FsYOG5Dc837z35Pw8pVMAaCRbUDWthxV1A+/s=
In-reply-to: <4CF661C7.2020103@xxxxxxxxxxx>
References: <AANLkTikzCpQ1j9uWGSTY9TEguVDvAB5AVYtbDtdePFci@xxxxxxxxxxxxxx> <4CF661C7.2020103@xxxxxxxxxxx>
While the copy operation is in progress, simply unplug the usb device and then replug.
The issue can be seen from XFS (2.6.31) onwards, I am trying to figure out the changes between and 2.6.31.
One thing I noticed is - there is difference in speed for 2 versions - in case of 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.
I am using MIPS at the moment with VIPT(fixes included)

Please let me know if this information is useful.
Amit Sahrawat
On Wed, Dec 1, 2010 at 8:25 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
On 12/1/10 1:14 AM, Amit Sahrawat wrote:
> Dear Member,
> I am getting following corruption on XFS formatted disk during a simple copy operation:
> sd 9:0:0:0: Attached scsi removable disk sdc
> sd 9:0:0:0: Attached scsi generic sg2 type 0
> XFS mounting filesystem sdc2
> Starting XFS recovery on filesystem: sdc2 (logdev: internal)
> XFS: xlog_recover_process_data: bad transaction
> XFS: log mount/recovery failed: error 5
> XFS: log mount failed

hm, that's not a simple copy operation, that is a mount failing;
your log appears to be corrupted.

offhand I'm going to blame it on having a write cache enabled
on your drive, and having barriers either off, or not working


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