From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Eric Sandeen <sandeen@sandeen.net>,
Amit Sahrawat <amit.sahrawat83@gmail.com>
Subject: Re: XFS hangs
Date: Wed, 22 Dec 2010 09:04:56 +0100 [thread overview]
Message-ID: <201012220904.56914@zmi.at> (raw)
In-Reply-To: <20101222060254.GH4907@dastard>
[-- Attachment #1.1: Type: Text/Plain, Size: 2265 bytes --]
On Mittwoch, 22. Dezember 2010 Dave Chinner wrote:
> For future reference, when you are reporting a problem you need to
> be specific about what you were doing to cause the problem you are
> reporting. Describe your kernel, your storage, your test case, any
> errors that occurred before the problem you are reporting, etc.
>
> We need this information to make any sense of your bug report, but
> I'm getting tired of having to ask for it every time you report a
> problem. The more information you put in your bug report, the more
> likely we are to be able to help you. We don't have unlimited
> amounts of time (or patience) to drag all the basic details of your
> problem out of you over 3 or 4 emails, so including it up front will
> help a lot....
Should I update this section?
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
We should probably just send that link to people so you don't have to
write long texts all the time.
Maybe above section should be updated to:
Things to include are what version of XFS you are using and version of
the kernel. If you have problems with userland packages please report
the version of the package you are using.
If the problem relates to a particular filesystem, the output from the
xfs_info(8) command and any mount(8) options in use will also be useful
to the developers.
If you experience an oops, please run it through ksymoops so that it can
be interpreted. Also describe what you were doing, if you can repeat it,
and describe you kernel, storage, test case, if there was a hardware
problem before, etc.
If you have a filesystem that cannot be repaired, make sure you have
xfsprogs 3.1.x or later and run xfs_metadump(8) to capture the metadata
(which obfuscates filenames and attributes to protect your privacy) and
make the dump available for someone to analyse.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// ****** Radiointerview zum Thema Spam ******
// http://www.it-podcast.at/archiv.html#podcast-100716
//
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-22 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 5:35 XFS hangs Amit Sahrawat
2010-12-22 6:02 ` Dave Chinner
[not found] ` <AANLkTin44EAmOtYrE4bd==ux4s11_QfDLVd7ROSf_+K3@mail.gmail.com>
2010-12-22 6:57 ` Amit Sahrawat
2010-12-22 8:04 ` Michael Monnerie [this message]
2010-12-22 9:12 ` Amit Sahrawat
2010-12-22 16:08 ` Eric Sandeen
2010-12-22 9:50 ` 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=201012220904.56914@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=amit.sahrawat83@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox