Linux NFS development
 help / color / mirror / Atom feed
From: Michael Buesch <fsdeveloper@yahoo.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: neilb@cse.unsw.edu.au, nfs@lists.sourceforge.net, "Lever,
	Charles" <Charles.Lever@netapp.com>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Zeev Fisher <Zeev.Fisher@il.marvell.com>
Subject: Re: processes stuck in D state
Date: Tue, 6 May 2003 17:41:50 +0200	[thread overview]
Message-ID: <200305061742.14032.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <shsel3c85ks.fsf@charged.uio.no>

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 06 May 2003 17:20, Trond Myklebust wrote:
> >>>>> " " =3D=3D Michael Buesch <fsdeveloper@yahoo.de> writes:
>      > Hi!  Please take a look at this problem:
>      >
>      > [linux-kernel-mailing-list thread]
>      > http://marc.theaimsgroup.com/?t=3D98639966100003&r=3D1&w=3D2
>
> If I can hazard a guess: someone is firewalling the lockd port and/or
> the statd port.
>
> Either mount using the 'nolock' option, or fix the firewall (see the
> HOWTO and/or FAQ).

To reproduce the problem:
=2D - mount some nfs from a server in your lan.
=2D - Open an app, that uses the mounted fs. I've simply opened a
  konqueror-window for the directory where the nfs is mounted.
=2D - shut down or crash the server or just pull the network-cable.
=2D - Now the konqueror-process is nonkillable in D state. There's no
  chance to kill it.

I've tried it with all firewalls disabled, but the problem resists.

> Cheers,
>   Trond

@linux-kernel-mailing-list: I've posted a thread to nfs-mailing list with
the same topic as in lkml. IMHO this is the better list for this problem. :)

=2D --=20
Regards Michael B=FCsch
http://www.8ung.at/tuxsoft
 17:34:35 up  1:26,  5 users,  load average: 1.52, 1.32, 1.13
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+t9fWoxoigfggmSgRAvrcAJ4i+i3V+kcRd+kLHS7cb2WDZDHKsQCfWljd
rwtAFK4ONkJHzVck03t7F5U=3D
=3DgHuP
=2D----END PGP SIGNATURE-----



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-05-06 15:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 14:51 processes stuck in D state Michael Buesch
2003-05-06 15:20 ` Trond Myklebust
2003-05-06 15:41   ` Michael Buesch [this message]
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           ` [NFS] " Michael Buesch
  -- strict thread matches above, loose matches on Subject: below --
2003-05-06 15:18 Lever, Charles
2003-05-06 15:47 Lever, Charles
2003-05-06 17:09 pwitting
2003-05-06 17:31 ` Michael Buesch
2003-05-06 18:32 Guolin Cheng
2004-02-18 16:33 Processes " Olaf Kirch

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=200305061742.14032.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=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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