From: Michael Buesch <fsdeveloper@yahoo.de>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: <nfs@lists.sourceforge.net>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
"Zeev Fisher" <Zeev.Fisher@il.marvell.com>
Subject: Re: [NFS] processes stuck in D state
Date: Tue, 6 May 2003 17:56:24 +0200 [thread overview]
Message-ID: <200305061756.36568.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C611312747A@lavender-fe.eng.netapp.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 06 May 2003 17:47, Lever, Charles wrote:
> does the problem persist after you reconnect the network cable?
> what happens when the server becomes available again?
no. If server is available again, the process wakes up from D.
But like man mount says:
[snip] The process cannot be interrupted or killed unless you also specify intr. [/snip]
The process should be killable while the cable is pulled.
But that's not the case, although intr is in fstab.
> are you mounting with UDP or TCP?
uh. How to find it out? :)
- --
Regards Michael Büsch
http://www.8ung.at/tuxsoft
17:53:19 up 1:44, 5 users, load average: 1.04, 1.05, 1.06
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+t9s0oxoigfggmSgRAkDPAKCFMeEGvS3KUhwn0bNQngKRK6h2fwCdEcv/
U2ttfZ6Mm8Sazuksfn4UUrY=
=M5Kh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-05-06 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 15:47 [NFS] processes stuck in D state Lever, Charles
2003-05-06 15:56 ` Michael Buesch [this message]
[not found] <200305061652.13280.fsdeveloper@yahoo.de>
[not found] ` <shsel3c85ks.fsf@charged.uio.no>
2003-05-06 15:41 ` Michael Buesch
2003-05-06 16:05 ` Trond Myklebust
2003-05-06 16:30 ` Michael Buesch
2003-05-06 16:54 ` Trond Myklebust
2003-05-06 17:32 ` Michael Buesch
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=200305061756.36568.fsdeveloper@yahoo.de \
--to=fsdeveloper@yahoo.de \
--cc=Charles.Lever@netapp.com \
--cc=Zeev.Fisher@il.marvell.com \
--cc=linux-kernel@vger.kernel.org \
--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