From: Dieter Stueken <stueken@conterra.de>
To: linux-kernel@vger.kernel.org
Subject: Re: nfsd oops with 2.6.5-rc2-mm4
Date: Sun, 28 Mar 2004 00:17:09 +0100 [thread overview]
Message-ID: <40660B75.7000605@conterra.de> (raw)
Frank Denis wrote:
> Version 3. I can give version 2 a try but there will probably
> a significant loss of performance :(
probably better than a total loss of performance :-)
> Unfortunately this is a production environment and I can hardly
> switch the Solaris box off in order to make it sure that it is
> triggering the bug.
Same here. I set up a NFS-server for test and let the Sun
mount the data in a temporary directory to verify the situation.
The test-server may crash, but the sun will survive. After you
stopped the test on the sun, you might have to reboot your
test-server to be able to unmount the disk on the sun again.
>> I reverted to 2.6.2-rc2-mm3, the server didn't crash after 6 hours. Crossing fingers...
>
> Pointless.
>
> 2.6.2-rc2-mm3 just crashed the same way.
Yes, all 2.6.x seem to be affected. My good old 2.4.19 runs since 6 month.
I started to scan the 2.5.x patches for changes on nfsd, to find by which
one this kind of trouble was caused....
Dieter.
next reply other threads:[~2004-03-27 23:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 23:17 Dieter Stueken [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-27 19:10 nfsd oops with 2.6.5-rc2-mm4 Dieter Stueken
2004-03-27 20:03 ` Frank Denis
2004-03-27 20:40 ` Frank Denis
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=40660B75.7000605@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.