From: Dave Chinner <david@fromorbit.com>
To: Julian Wollrath <jwollrath@web.de>
Cc: xfs@oss.sgi.com
Subject: Re: Null pointer dereference and following traces on 3.9-rc1
Date: Mon, 11 Mar 2013 09:56:00 +1100 [thread overview]
Message-ID: <20130310225600.GL23616@dastard> (raw)
In-Reply-To: <20130310154900.673deee0@ilfaris>
On Sun, Mar 10, 2013 at 03:49:00PM +0100, Julian Wollrath wrote:
> Hello,
>
> after a xfs_fsr run I found the following in my syslog:
If you can reproduce this, please run an event trace gathering
the xfs_swap_extent* trace points while xfs_fsr is running so I can
determine if/why the swap extents code is corrupting inodes.
# trace-cmd record -e xfs_swap_extents\* xfs_fsr .....
<crash>
<kill xfs_fsr>
# trace-cmd report > trace_report.txt
Read here for a bit more detail on trace-cmd:
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:[~2013-03-10 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 14:49 Null pointer dereference and following traces on 3.9-rc1 Julian Wollrath
2013-03-10 22:56 ` Dave Chinner [this message]
2013-03-15 14:57 ` Julian Wollrath
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=20130310225600.GL23616@dastard \
--to=david@fromorbit.com \
--cc=jwollrath@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox