From: Dave Chinner <david@fromorbit.com>
To: "J. Ellis" <jellis@dhnet.us>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfsdump INTERRUPT issue
Date: Mon, 3 Dec 2012 08:10:23 +1100 [thread overview]
Message-ID: <20121202211023.GF12955@dastard> (raw)
In-Reply-To: <CCDF949D.B03CC%jellis@dhnet.us>
On Sat, Dec 01, 2012 at 11:03:57AM -0500, J. Ellis wrote:
> I'm trying to prepare a question regarding an xfsdump INTERRUPT error I'm
> getting, and I'm trying to follow the guidelines for reporting such issues
> here:
>
> http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_r
> eporting_a_problem.3F
>
> But these last two instructions I'm having a problem finding the information
> on how to generate:
>
>
> xfs_info output on the filesystem in question (I tried xfs_info /dev/sdc,
> but it keeps saying for each drive that it's not a mounted xfs system IIRC)
$ man xfs_info
....
xfs_info [ -t mtab ] mount-point
....
> dmesg output showing all error messages and stack traces
Run the dmesg command....
> Then you need to describe your workload that is causing the problem, and a
> demonstration of the bad behavior that is occurring. If it is a performance
> problem, then 30s - 1 minute samples of:
> 1. iostat -x -d -m 5
> 2. vmstat 5
>
>
> Do I run this simultaneously while xfstools are working? I'm also not sure
> what's meant by describe your workload. Can someone step me through this?
Do you have a performance problem? I don't think you have - your problem is
that xfsdump is failing for some reason - so this information is
unnecessary.
As to your workload, your problem is xfsdump is failing for some
reason. Hence we need to know roughly what xfsdump is running on.
i.e. describe the directory structure/filesystem contents being
backed up....
BTW, don't expect responses to questions in a hour late on friday
night/weekends - if you are lucky someone will be in front of their
computer over a weekend, sometimes you are not so lucky...
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-12-02 21:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 16:03 xfsdump INTERRUPT issue J. Ellis
2012-12-01 17:39 ` Jeffrey Ellis
2012-12-02 1:40 ` Stan Hoeppner
2012-12-03 16:49 ` J. Ellis
2012-12-03 21:34 ` Dave Chinner
2012-12-03 22:27 ` Jeffrey Ellis
2012-12-05 0:32 ` Stan Hoeppner
2012-12-05 1:18 ` J. Ellis
2012-12-05 3:32 ` Stan Hoeppner
2012-12-04 19:46 ` J. Ellis
2012-12-04 22:56 ` Stan Hoeppner
2012-12-04 23:07 ` Jeffrey Ellis
2012-12-05 22:19 ` Dave Chinner
2012-12-02 21:10 ` Dave Chinner [this message]
2012-12-02 21:16 ` Jeffrey Ellis
[not found] <CCE505AA.B05B7%jellis@dhnet.us>
2012-12-06 1:38 ` Stan Hoeppner
2012-12-06 2:08 ` Jeffrey Ellis
2012-12-06 2:40 ` Stan Hoeppner
[not found] ` <6F909666-9DFE-43F1-973D-170B892F9C5B@gmail.com>
2012-12-06 9:29 ` Stan Hoeppner
2012-12-06 10:35 ` Jeffrey Ellis
2012-12-07 10:16 ` Dave Chinner
2012-12-07 16:15 ` Jeffrey Ellis
2012-12-07 22:59 ` Dave Chinner
2012-12-07 23:16 ` Jeffrey Ellis
2012-12-07 21:04 ` Stan Hoeppner
2012-12-07 22:58 ` Dave Chinner
2012-12-07 23:26 ` Stan Hoeppner
2012-12-08 1:31 ` Dave Chinner
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=20121202211023.GF12955@dastard \
--to=david@fromorbit.com \
--cc=jellis@dhnet.us \
--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