From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Even slower NFS mounting with 2.4.0
Date: Sun, 7 Jan 2001 18:23:31 +0100 (CET) [thread overview]
Message-ID: <14936.42515.988953.602296@charged.uio.no> (raw)
In-Reply-To: <E14FJIN-0002xW-00@the-village.bc.nu>
In-Reply-To: <shs1yufxqvq.fsf@charged.uio.no> <E14FJIN-0002xW-00@the-village.bc.nu>
>>>>> " " == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>> > This is caused by 2.3/2.4 changes in the network code error
>> > reporting of unreachables with UDP I suspect. It looks like
>> > the NFS code hasn't yet caught up with the error notification
>> > stuff
>>
>> No. It was the fact that he was forgetting to start the
>> portmapper before mounting an NFS partition with locking
>> enabled.
> Its both. If you support the error notification then you see
> the PORT UNREACH and you abandon early even if the user makes
> that error
Hmm... How should we respond to that sort of thing? In principle the
NFS layer supposes that if we have a hard mount, then unreachable
ports etc are a temporary problem, and we should wait them out. (In
fact, I've made an RPC 'ping' routine that improves on that behaviour
but which unfortunately didn't make it into 2.4.0.)
If we want to check that the port is reachable at the moment when we
mount, I think we should concentrate on making 'mount' more
intelligent. Perhaps have it RPC-ping the various ports (including the
local portmapper when we specify locking)?
Cheers,
Trond
-
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 parent reply other threads:[~2001-01-07 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E14FJIN-0002xW-00@the-village.bc.nu>
[not found] ` <shs1yufxqvq.fsf@charged.uio.no>
2001-01-07 17:23 ` Trond Myklebust [this message]
2001-01-07 17:33 ` Alan Cox
2001-01-05 23:25 Christian Ullrich
2001-01-06 5:14 ` Mohammad A. Haque
2001-01-06 8:18 ` Christian Ullrich
2001-01-06 9:46 ` Russell King
2001-01-06 15:27 ` 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=14936.42515.988953.602296@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®