All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Amit Sahrawat <amit.sahrawat83@gmail.com>
Cc: sandeen-xfs@sandeen.net, Eric Sandeen <sandeen@sandeen.net>,
	xfs@oss.sgi.com
Subject: Re: XFS file system corruption(Return Bad Transaction) kernel - 2.6.34
Date: Thu, 2 Dec 2010 13:16:09 +1100	[thread overview]
Message-ID: <20101202021609.GV16922@dastard> (raw)
In-Reply-To: <AANLkTikzCpQ1j9uWGSTY9TEguVDvAB5AVYtbDtdePFci@mail.gmail.com>

On Wed, Dec 01, 2010 at 12:44:58PM +0530, 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
> [root@localhost TEGRA]#

"TEGRA" - You're running on an ARM device? If so, what kernel are
you running? i.e. does it have the VIVT cache aliasing fixes in it?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2010-12-02  2:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01  7:14 XFS file system corruption(Return Bad Transaction) kernel - 2.6.34 Amit Sahrawat
2010-12-01 14:55 ` Eric Sandeen
2010-12-02  3:40   ` Amit Sahrawat
2010-12-02  3:56     ` Eric Sandeen
2010-12-02  4:09       ` Amit Sahrawat
2010-12-02  4:13     ` Dave Chinner
2010-12-02  4:38       ` Amit Sahrawat
2010-12-02 12:23         ` Amit Sahrawat
2010-12-02  2:16 ` Dave Chinner [this message]
2010-12-02  3:41   ` Amit Sahrawat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101202021609.GV16922@dastard \
    --to=david@fromorbit.com \
    --cc=amit.sahrawat83@gmail.com \
    --cc=sandeen-xfs@sandeen.net \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.