From: Ethan Benson <erbenson@alaska.net>
To: linux-kernel@vger.kernel.org
Subject: nfs client serious problems under 2.2.20pre8/9
Date: Mon, 3 Sep 2001 19:18:49 -0800 [thread overview]
Message-ID: <20010903191849.D14519@plato.local.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
I have encountered a serious problem with nfs under 2.2.20pre8 and
pre9.
after some ammount of time (2 weeks under pre8, only a few hours under
pre9) most/all processes accessing an nfs filesystem go into
unkillable disk sleep, and the kernel starts spewing:
kernel: nfs: task 22509 can't get a request slot
over and over again endlessly. since processes using the filesystem
are unkillable i am unable to even forcabily umount the problematic
filesystem, seemingly the only way restore order is shutdown -r now :(
the server is an x86 running 2.2.19, knfs, with userland utils
version 0.3.1. the client is a powerpc running 2.2.20pre8 or pre9,
both exhibit this behavior. 2.2.19 on the client does NOT exhibit
this problem.
note that this seems to mostly get triggered on my daily cronjobs,
which simply tar up /etc to a tarball on the nfs filesystem, its
really not that intensive (/etc is only about 2.6MB or so). i have
other machines doing the same thing without incident (they are
currently running 2.4.9).
the server displays no unusal symtoms or any log entries that would
indicate trouble.
both client and server are using NFSv3.
please CC me any replies as i am not subscribed to l-k. thanks.
--
Ethan Benson
http://www.alaska.net/~erbenson/
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next reply other threads:[~2001-09-04 3:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 3:18 Ethan Benson [this message]
2001-09-04 7:48 ` nfs client serious problems under 2.2.20pre8/9 VDA
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=20010903191849.D14519@plato.local.lan \
--to=erbenson@alaska.net \
--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.