Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Michael Buesch <fsdeveloper@yahoo.de>
Cc: neilb@cse.unsw.edu.au,  nfs@lists.sourceforge.net
Subject: Re: processes stuck in D state
Date: 06 May 2003 17:20:35 +0200	[thread overview]
Message-ID: <shsel3c85ks.fsf@charged.uio.no> (raw)
In-Reply-To: <200305061652.13280.fsdeveloper@yahoo.de>

>>>>> " " == Michael Buesch <fsdeveloper@yahoo.de> writes:

     > Hi!  Please take a look at this problem:

     > [linux-kernel-mailing-list thread]
     > http://marc.theaimsgroup.com/?t=98639966100003&r=1&w=2

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).

Cheers,
  Trond


-------------------------------------------------------
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:20 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 [this message]
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           ` [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=shsel3c85ks.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=fsdeveloper@yahoo.de \
    --cc=neilb@cse.unsw.edu.au \
    --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