linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: linux-kernel@vger.kernel.org
Subject: [BUG] NFS in 2.4.20-pre6+ stalls
Date: Mon, 16 Sep 2002 16:54:48 -0600	[thread overview]
Message-ID: <200209162254.g8GMsmG00784@vindaloo.ras.ucalgary.ca> (raw)

  Hi, all. Just noticed this with 2.4.20-pre6 (and -pre7): NFS write
sometimes (usually) stalls for minutes at a time. This problem wasn't
there on 2.4.19. I've noticed this when writing a files around 1 MiB
or so (some a bit larger, some a bit smaller). It makes NFS almost
unusable. I've appended the kernel logs which come, at no extra
charge, with the problem. On the server, I see partial files (integral
number of wsize= blocks) during the stall. Eventually, the client
seems to recover and the rest of the file is written. The writing
application is in TASK_INTERRUPTIBLE state.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca
===============================================================================
nfs: task 125 can't get a request slot
nfs: task 126 can't get a request slot
nfs: task 127 can't get a request slot
nfs: task 128 can't get a request slot
nfs: task 129 can't get a request slot
nfs: task 130 can't get a request slot
nfs: task 131 can't get a request slot
nfs: task 132 can't get a request slot
nfs: task 133 can't get a request slot
nfs: task 134 can't get a request slot
nfs: task 135 can't get a request slot
nfs: task 136 can't get a request slot
nfs: task 137 can't get a request slot
nfs: task 138 can't get a request slot
nfs: task 139 can't get a request slot
nfs: task 140 can't get a request slot
nfs: task 141 can't get a request slot
nfs: task 142 can't get a request slot
nfs: task 143 can't get a request slot
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK
nfs: server fileserver OK

             reply	other threads:[~2002-09-16 22:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16 22:54 Richard Gooch [this message]
2002-09-16 23:10 ` [BUG] NFS in 2.4.20-pre6+ stalls Alan Cox
2002-09-17 18:41   ` Bill Davidsen
2002-09-25 12:41 Trond Myklebust
2002-09-25 15:30 ` Richard Gooch
2002-09-26 11:29   ` Trond Myklebust
2002-09-28 22:43     ` Richard Gooch

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=200209162254.g8GMsmG00784@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).