From: Eric Sandeen <sandeen@sandeen.net>
To: Martin Spott <Martin.Spott@mgras.net>
Cc: linux-xfs@oss.sgi.com
Subject: Re: Kernel crash with 2.6.29 + nfs + xfs (radix-tree)
Date: Sun, 07 Jun 2009 13:27:36 -0500 [thread overview]
Message-ID: <4A2C0698.9060800@sandeen.net> (raw)
In-Reply-To: <h0gtcd$136u$1@osprey.mgras.de>
Martin Spott wrote:
> Hi Christoph,
>
> Christoph Hellwig wrote:
>
>> Sorry guys, still haven't been able to track it down. Any chance one
>> of you could run with CONFIG_XFS_DEBUG enabled and see if it trips
>> over any of the asserts?
>
> "Say N unless you are an XFS developer, or you play one on TV."
>
> Very nice ;-)
>
> I'm have to regret that I'm neither an XFS developer nor do I pretend
> to be one. Yet, as I understand, I should see at least _some_ debug
> info via 'dmesg', if there is any.
CONFIG_XFS_DEBUG is more of addded checks and asserts, not so much in
the way of extra messages - at least, until you actually hit a problem.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-07 18:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090520003745.GA27491@samad.com.au>
2009-05-20 9:05 ` Kernel crash with 2.6.29 + nfs + xfs (radix-tree) Dave Chinner
2009-05-20 9:56 ` Alex Samad
2009-05-26 9:09 ` Christoph Hellwig
2009-05-27 2:54 ` Alex Samad
2009-06-04 11:26 ` Christoph Hellwig
2009-06-05 11:20 ` Martin Spott
2009-06-07 17:28 ` Martin Spott
2009-06-07 18:27 ` Felix Blyakher
2009-06-07 18:27 ` Eric Sandeen [this message]
2009-06-07 18:55 ` Martin Spott
2009-06-07 18:55 ` Christoph Hellwig
2009-06-07 20:00 ` Martin Spott
2009-06-07 20:44 ` Christoph Hellwig
2009-06-07 21:26 ` Martin Spott
2009-06-08 20:13 ` Martin Spott
2009-06-09 8:40 ` Christoph Hellwig
2009-05-27 17:21 ` Martin Spott
2009-05-27 18:05 ` Martin Spott
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=4A2C0698.9060800@sandeen.net \
--to=sandeen@sandeen.net \
--cc=Martin.Spott@mgras.net \
--cc=linux-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