From: Martin Spott <Martin.Spott@mgras.net>
To: linux-xfs@oss.sgi.com
Subject: Re: Kernel crash with 2.6.29 + nfs + xfs (radix-tree)
Date: Sun, 7 Jun 2009 18:55:21 +0000 (UTC) [thread overview]
Message-ID: <h0h2ep$8p0$1@osprey.mgras.de> (raw)
In-Reply-To: 4A2C0698.9060800@sandeen.net
Eric Sandeen wrote:
> 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.
The problem I see is actually not logged as a crash in the 'usual' way
(panics, oopses, traces the way I know), instead, the issue
materializes in tons of messages of the sort:
reconnect_path: npd != pd
reconnect_path: npd != pd
reconnect_path: npd != pd
.... on a thorougly checked filesystem, plus the NFS service ceasing
to serve clients. Obviously this is not covered by the added checks
which are introduced by CONFIG_XFS_DEBUG.
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-07 18:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 0:37 Kernel crash with 2.6.29 + nfs + xfs (radix-tree) Alex Samad
2009-05-20 9:05 ` Dave Chinner
2009-05-20 9:05 ` Dave Chinner
2009-05-20 9:56 ` Alex Samad
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
2009-06-07 18:55 ` Martin Spott [this message]
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='h0h2ep$8p0$1@osprey.mgras.de' \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.