From: Russell King <rmk@arm.linux.org.uk>
To: chris@chrullrich.de (Christian Ullrich)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Even slower NFS mounting with 2.4.0
Date: Sat, 6 Jan 2001 09:46:37 +0000 (GMT) [thread overview]
Message-ID: <200101060946.f069kbv18455@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20010106002531.A490@christian.chrullrich.de> from "Christian Ullrich" at Jan 06, 2001 12:25:31 AM
Christian Ullrich writes:
> About three weeks ago, I complained loudly about very slow NFS mounts
> involving a 2.2.17 server and a 2.2.18 client.
>
> Today, I complain loudly about *extremely* slow NFS mounts
> with the very same server and the same client now running 2.4.0.
In all cases, you need to either:
1. Provide the option "nolock" to turn of NFS file locking (which means
that things like elm can't lock mailboxes and will get upset if the
mailboxes are on a NFS partition).
2. before running the mount command:
a) make sure the loopback interface is up and running
b) ensure that the portmapper (called portmap or rpc.portmap) is
running.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-06 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 23:25 Even slower NFS mounting with 2.4.0 Christian Ullrich
2001-01-06 5:14 ` Mohammad A. Haque
2001-01-06 8:18 ` Christian Ullrich
2001-01-06 9:46 ` Russell King [this message]
2001-01-06 15:27 ` Alan Cox
[not found] <shs1yufxqvq.fsf@charged.uio.no>
[not found] ` <E14FJIN-0002xW-00@the-village.bc.nu>
2001-01-07 17:23 ` Trond Myklebust
2001-01-07 17:33 ` Alan Cox
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=200101060946.f069kbv18455@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=chris@chrullrich.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox