From: Andi Kleen <andi@firstfloor.org>
To: Paul Anderson <pha@umich.edu>
Cc: xfs@oss.sgi.com
Subject: Re: XFS/Linux Sanity check
Date: Mon, 02 May 2011 10:09:59 -0700 [thread overview]
Message-ID: <m2zkn5yqoo.fsf@firstfloor.org> (raw)
In-Reply-To: <BANLkTik4YjSr7-VA+f9Sh+UxvKfFKMy=+w@mail.gmail.com> (Paul Anderson's message of "Mon, 2 May 2011 11:47:48 -0400")
Paul Anderson <pha@umich.edu> writes:
>
> md apparently does not support barriers, so we are badly exposed in
MD barriers for RAID-0 were added in 2.6.33, but very recent kernels
have much improved barriers again.
> Secondly, I welcome suggestions about which version of the linux
> kernel you'd prefer to hear bug reports about, as well as what kinds
Kernel developers usually want reports about the newest versions,
ideally with enough information to debug the problem
(that is backtraces etc.)
When you have a hang but the console is still active you can also just
dump the threads with sysrq-t
Often when things hang it's the underlying IO subsystem (driver, IO device).
-Andi
--
ak@linux.intel.com -- Speaking for myself only
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-05-02 17:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 15:47 XFS/Linux Sanity check Paul Anderson
2011-05-02 17:09 ` Andi Kleen [this message]
2011-05-02 17:13 ` Emmanuel Florac
2011-06-11 1:33 ` FYI: LSI rebuilding; and XFS speed V. raw - hints on maxing out 'dd'....(if not already obvious) Linda Walsh
2011-06-11 9:30 ` Emmanuel Florac
2011-06-11 16:48 ` Linda Walsh
2011-05-03 3:18 ` XFS/Linux Sanity check Dave Chinner
2011-05-03 8:58 ` Michael Monnerie
2011-05-03 16:05 ` Paul Anderson
2011-05-04 10:36 ` Stan Hoeppner
2011-05-04 6:18 ` Stan Hoeppner
2011-05-04 1:10 ` Stan Hoeppner
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=m2zkn5yqoo.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=pha@umich.edu \
--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