From: "Mohammad A. Haque" <mhaque@haque.net>
To: Christian Ullrich <chris@chrullrich.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Even slower NFS mounting with 2.4.0
Date: Sat, 06 Jan 2001 00:14:17 -0500 [thread overview]
Message-ID: <3A56A9A9.ADC5755A@haque.net> (raw)
In-Reply-To: <20010106002531.A490@christian.chrullrich.de>
Hrm. I'm not seeing this problem on my setups.
Did you send details about your configurationlast time .. Could you
resend?
Christian Ullrich wrote:
>
> Hello!
>
> 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.
>
> Using 2.2.18, every mount took about 15 seconds, now, using 2.4.0,
> every mount takes exactly five minutes, which is way too long.
>
> According to syslog, the server begins and completes its operations
> related to the mount in under one second, so it seems to me that
> mount on the client just takes a nap in D state.
> Although the messages in the client's syslog look critical to me,
> once the fs is mounted, it works fine.
>
> Syslog on client:
>
> Jan 6 00:18:06 c kernel: portmap: server localhost not responding, timed out
> Jan 6 00:19:46 c kernel: portmap: server localhost not responding, timed out
> Jan 6 00:19:46 c kernel: lockd_up: makesock failed, error=-5
> Jan 6 00:21:26 c kernel: portmap: server localhost not responding, timed out
>
> I called the mount command five minutes before the final message above.
>
> I tried NFS with and without NFSv3 code, with no change at all.
>
> Please help me.
--
=====================================================================
Mohammad A. Haque http://www.haque.net/
mhaque@haque.net
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
batmanppc@themes.org
=====================================================================
-
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 5:14 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 [this message]
2001-01-06 8:18 ` Christian Ullrich
2001-01-06 9:46 ` Russell King
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=3A56A9A9.ADC5755A@haque.net \
--to=mhaque@haque.net \
--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