From: Eric Sandeen <sandeen@sandeen.net>
To: Michael Ole Olsen <gnu@gmx.net>
Cc: xfs <xfs@oss.sgi.com>
Subject: Re: xfs+nfs crash in 2.6.30 and 2.6.30.1
Date: Tue, 14 Jul 2009 23:00:58 -0500 [thread overview]
Message-ID: <4A5D547A.9040005@sandeen.net> (raw)
In-Reply-To: <20090715030046.GA28592@rlogin.dk>
Michael Ole Olsen wrote:
> radix_tree_tag_set/xfs_inode_set_reclaim_tag crash
>
> I keep getting kernel crashes with xfs+lvm2+mdadm (raid6) - correct in sync,
> all xfs partitions checked for corruption (but there were none, but the crashes persists).
>
> The raid6 has just resynced now because of this kernel hang.
>
> 2.6.30 and 2.6.30.1 kernels on my nfsv3 server keep crashing, both with/without SMP, dynticks,
> selinux (although selinux for some reason seems to make it crash very often)
Thanks, I've pasted this info into the bug report; It's unlikely that
it's a stack issue I think - the hint about selinux making it worse may
be useful.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-07-15 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 3:00 xfs+nfs crash in 2.6.30 and 2.6.30.1 Michael Ole Olsen
2009-07-15 3:46 ` Christoph Hellwig
2009-07-15 4:00 ` Eric Sandeen [this message]
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=4A5D547A.9040005@sandeen.net \
--to=sandeen@sandeen.net \
--cc=gnu@gmx.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