From: Dieter Stueken <stueken@conterra.de>
To: linux-kernel@vger.kernel.org
Subject: Re: nfsd oops with 2.6.5-rc2-mm4
Date: Sat, 27 Mar 2004 20:10:18 +0100 [thread overview]
Message-ID: <4065D19A.1040903@conterra.de> (raw)
Frank wrote:
> I got a reproducible oops after a few minutes with a 2.6.5-rc2-mm4 kernel.
> ...
> [<c01e6a8d>] nfsd_readdir+0x69/0xe8
was some exported directory quite big? Try running a "find /mnt/..." on
the client to see when exactly it fails. I observe similar behavior
when reading huge directories of some 1000 entries. What nfs version
are you using? You may try "mount -o nfsvers=2 ..." or 3.
My own Oops seems to be reproducible when using a Sun (2.8) as
client, only. It did not occur when using nfsV2. I also failed
to reproduce the bug when mounting by an other Linux client.
So may be we observe two different bugs here.
With that instability observed, I won't/can't switch to 2.6.x for
my system in production :-( Can I help somehow? Making a TCP-dump?
Try some patches?
Dieter.
--
Dieter Stüken, con terra GmbH, Münster
stueken@conterra.de
http://www.conterra.de/
(0)251-7474-501
next reply other threads:[~2004-03-27 19:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 19:10 Dieter Stueken [this message]
2004-03-27 20:03 ` nfsd oops with 2.6.5-rc2-mm4 Frank Denis
2004-03-27 20:40 ` Frank Denis
-- strict thread matches above, loose matches on Subject: below --
2004-03-27 23:17 Dieter Stueken
2004-03-27 13:07 Jedi/Sector One
2004-03-28 2:30 ` Linus Torvalds
2004-03-28 2:48 ` Andrew Morton
2004-03-28 8:05 ` Frank Denis
[not found] ` <1080511633.5553.29.camel@lade.trondhjem.org>
2004-03-29 1:03 ` Neil Brown
2004-03-29 2:44 ` Linus Torvalds
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=4065D19A.1040903@conterra.de \
--to=stueken@conterra.de \
--cc=linux-kernel@vger.kernel.org \
/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.