From: Dave Chinner <david@fromorbit.com>
To: Kamal Dasu <kdasu.kdev@gmail.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs filesystem corruption with kernel 2.6.37
Date: Sun, 4 Nov 2012 09:25:18 +1100 [thread overview]
Message-ID: <20121103222518.GH29378@dastard> (raw)
In-Reply-To: <37CBCD87-5B71-4B9C-8FAE-5BBF85804983@gmail.com>
On Fri, Nov 02, 2012 at 09:57:27PM -0400, Kamal Dasu wrote:
> Dave,
>
>
> >
> > 0x780dbd80007f248
> >
> > Once again it's corruption in the upper 32 bits of the 64 bit number.
> > Those bits should be zero. Perhaps looking at all the trace events
> > from recovery might give you a closer approximation of where the bad
> > extent records is found....
>
> I have been trying to use the xfs_db xfs_logprint, how ever
> xfs_logprint bails out when it finds an error.
$ man xfs_logprint
....
-c Attempt to continue when an error is detected.
> How do I look at
> trace events ?.
Documentation/trace/events.txt
Or better yet, use trace-cmd as suggested in the FAQ:
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-11-03 22:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 13:45 xfs filesystem corruption with kernel 2.6.37 Kamal Dasu
2012-10-25 22:47 ` Dave Chinner
2012-11-01 19:30 ` Kamal Dasu
2012-11-02 1:27 ` Dave Chinner
2012-11-02 16:34 ` Kamal Dasu
2012-11-02 22:55 ` Dave Chinner
2012-11-03 1:57 ` Kamal Dasu
2012-11-03 22:25 ` Dave Chinner [this message]
2012-11-09 21:18 ` Kamal Dasu
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=20121103222518.GH29378@dastard \
--to=david@fromorbit.com \
--cc=kdasu.kdev@gmail.com \
--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.