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 17:28:45 +0000 (UTC) [thread overview]
Message-ID: <h0gtcd$136u$1@osprey.mgras.de> (raw)
In-Reply-To: 20090604112657.GA10738@infradead.org
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. Apparently the kernel is now having
XFS with debugging enabled:
Jun 7 18:53:33 isnix1 kernel: SGI XFS with ACLs, security attributes, large block/inode numbers, debug enabled
Jun 7 18:53:33 isnix1 kernel: SGI XFS Quota Management subsystem
Jun 7 18:53:33 isnix1 kernel: XFS mounting filesystem cciss/c0d0p2
[...]
.... but aside from the well-known messages as:
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery
directory
NFSD: unable to find recovery directory /var/lib/nfs/v4recovery
NFSD: starting 90-second grace period
reconnect_path: npd != pd
reconnect_path: npd != pd
reconnect_path: npd != pd
[...]
.... I'm unable to find any helpful information in this context.
Anything I could try - this sunday evening ?
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 17:29 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 [this message]
2009-06-07 18:27 ` Felix Blyakher
2009-06-07 18:27 ` Eric Sandeen
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='h0gtcd$136u$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.