Linux NFS development
 help / color / mirror / Atom feed
From: David Rees <dbr@greenhydrant.com>
To: NFS <nfs@lists.sourceforge.net>
Subject: Re: NFS read ok, write ok, simultaneous R+W=TERRIBLE
Date: Thu, 5 Dec 2002 11:55:00 -0800	[thread overview]
Message-ID: <20021205115500.A9837@greenhydrant.com> (raw)
In-Reply-To: <CFEAJJEGMGECBCJFLGDBGEIHCJAA.hammer@clarkisland.com>; from hammer@clarkisland.com on Thu, Dec 05, 2002 at 10:35:14AM -0800

On Thu, Dec 05, 2002 at 10:35:14AM -0800, Jake Hammer wrote:
> 
> > Also, are the NFSd's in disk wait?
> 
> Could you tell me how to check this? I'll be pleased to report once I know
> how.
> 
> > If they are not, then
> > this would be a clearer indications that the nfs subsystem
> > may be to blame.  We usually see all the daemons in
> > disk wait when we are really pounding one of the these
> > boxes.
> 
> Yes, I'd love to be able to check. Please let me know how. This sounds
> interesting.

I doubt that the NFSd's are in disk wait given that you mentioned that 4
of them are sucking up CPU as indicated in your original post:
http://marc.theaimsgroup.com/?l=linux-nfs&m=103905720718370&w=2

However, to check if a process is indeed in disk wait, running top will
show you.  Under the stat column, instead of a R, you will see D
indicating a process waiting on a disk command to return.

Sounds like a legitimate problem with the NFS server code, I'll also see
if I can reproduce.

-Dave


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2002-12-05 19:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05  2:44 NFS read ok, write ok, simultaneous R+W=TERRIBLE Jake Hammer
2002-12-05  5:01 ` Eric Whiting
2002-12-05  5:55   ` Jake Hammer
2002-12-06 17:58     ` Paul Haas
2002-12-05 17:28 ` canon
2002-12-05 18:25   ` Eff Norwood
2002-12-05 18:35   ` Jake Hammer
2002-12-05 19:55     ` David Rees [this message]
2002-12-06  0:04     ` canon
     [not found] <3DEEEC53.D24A1933@amis.com>
2002-12-05  6:27 ` Jake Hammer
  -- strict thread matches above, loose matches on Subject: below --
2002-12-05 10:32 trmcneal
     [not found] <20021205192917.GA16871@hpti.com>
2002-12-05 19:47 ` Jake Hammer

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=20021205115500.A9837@greenhydrant.com \
    --to=dbr@greenhydrant.com \
    --cc=nfs@lists.sourceforge.net \
    /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