From: Christoph Hellwig <hch@infradead.org>
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:46:18 -0400 [thread overview]
Message-ID: <20090715034618.GA21478@infradead.org> (raw)
In-Reply-To: <20090715030046.GA28592@rlogin.dk>
On Wed, Jul 15, 2009 at 05:00:47AM +0200, Michael Ole Olsen wrote:
> Everything was stable on server+client until the server got 2.6.30 kernel,
> the mdadm raid6 only works in 2.6.30 or above - mdadm fails to initialize it in
> anything else, so cannot downgrade (custom reshape to raid6 using echo into /sys,
> all Q blocks on one disk).
>
> I have experimented with mount options on the client, and the client has
> been stable with these mount options before, when the server had a kernel
> below 2.6.30
Yes, we had a few reports of this already, but not been able to track it
down. Your instrcution below will be very helpful to reproduce and test
it, I will looks at it on thursday when I get back home to my test
systems.
> I saw someone talking about kernel stack size would be the cause for this xfs+nfs problem,
> is there anything to this?
Unlikely, it looks like problem in the XFS inode cache code introduced
in 2.6.29.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-15 3:45 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 [this message]
2009-07-15 4:00 ` Eric Sandeen
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=20090715034618.GA21478@infradead.org \
--to=hch@infradead.org \
--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