From: Jakob Oestergaard <jakob@unthought.net>
To: Greg Stark <gsstark@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: More tests [Was: Problem with read blocking for a long time on /dev/scd1]
Date: Wed, 8 Jan 2003 05:03:03 +0100 [thread overview]
Message-ID: <20030108040303.GE3960@unthought.net> (raw)
In-Reply-To: <87n0mxt8md.fsf@stark.dyndns.tv>
On Mon, Dec 23, 2002 at 03:58:02AM -0500, Greg Stark wrote:
> Jakob Oestergaard <jakob@unthought.net> writes:
>
...
> When your process is blocked, what wait channel does ps -elf list for it?
> What system call does strace -T show it executing and for how long?
On the NFS server, knfsd and kupdated will block on "wait_on_b" (WCHAN
in top).
I guess an strace on the NFS client would just show the process waiting
in some open/read/write/close code, waiting for NFS/RPC. Not much good.
The hangs last for approximately 5 seconds, sometimes around 10.
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
next prev parent reply other threads:[~2003-01-08 3:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 0:49 Problem with read blocking for a long time on /dev/scd1 Gregory Stark
2002-12-21 1:28 ` Greg Stark
2002-12-21 6:14 ` Greg Stark
2002-12-22 16:13 ` More tests [Was: Problem with read blocking for a long time on /dev/scd1] Greg Stark
2002-12-22 20:13 ` Jakob Oestergaard
2002-12-23 8:58 ` Greg Stark
2002-12-27 15:36 ` Jakob Oestergaard
2003-01-08 4:03 ` Jakob Oestergaard [this message]
2002-12-23 18:02 ` Problem with read blocking for a long time on /dev/scd1 Krzysztof Halasa
-- strict thread matches above, loose matches on Subject: below --
2003-01-08 12:03 More tests [Was: Problem with read blocking for a long time on /dev/scd1] Andrey Borzenkov
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=20030108040303.GE3960@unthought.net \
--to=jakob@unthought.net \
--cc=gsstark@mit.edu \
--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.