From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "List User" <lists@chaven.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: NFS mounting delays w/ 2.4.x kernel?
Date: 15 Feb 2001 10:53:53 +0100 [thread overview]
Message-ID: <shshf1we0ge.fsf@charged.uio.no> (raw)
In-Reply-To: <20010215002012.A21227@gamersgold.net> <031001c096e9$2c437a60$160912ac@stcostlnds2zxj>
In-Reply-To: "List User"'s message of "Wed, 14 Feb 2001 18:49:29 -0600"
>>>>> " " == List User <lists@chaven.com> writes:
> I've seen reference to this before (I think on this list) but
> didn't pay attention to them at the time. I am now running
> into this problem myself. I've just upgraded one of my NFS
> servers here from 2.2.17 -> 2.4.1 ).
> I'm running the user-space server nfs-server-2.2beta48 (tried
> beta47 as well). Current versions of mount, et al. When
> booting I get the following errors:
> --------------------------- Mounted devfs on /dev Trying to
> unmount old root ... okay Freeing unused kernel memory: 228k
> freed Adding Swap: 1048568k swap-space (priority -1) portmap:
> server localhost not responding, timed out portmap: server
> localhost not responding, timed out lockd_up: makesock failed,
> error=-5 portmap: server localhost not responding, timed out
> -----------------------------
You need to add 'nolock' to your mount options. Unfsd doesn't support
NLM locking, and it's causing the lockd daemon to be started (which
again requires the portmapper to be installed etc.).
Cheers,
Trond
prev parent reply other threads:[~2001-02-15 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 0:20 doing RAID 0 with HPT370 Bradley Kite
2001-02-15 0:19 ` David D.W. Downey
2001-02-15 0:45 ` Mark Hahn
2001-02-15 0:49 ` NFS mounting delays w/ 2.4.x kernel? List User
2001-02-15 9:53 ` Trond Myklebust [this message]
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=shshf1we0ge.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@chaven.com \
/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