From: Greg Lindahl <lindahl@keyresearch.com>
To: "David B. Ritch" <dritch@hpti.com>
Cc: NFS mailing list <nfs@lists.sourceforge.net>,
Craig Tierney <ctierney@hpti.com>
Subject: Re: NFS mount/umount problem
Date: Thu, 16 Jan 2003 12:00:18 -0800 [thread overview]
Message-ID: <20030116200018.GA1253@wumpus.internal.keyresearch.com> (raw)
In-Reply-To: <1042744656.3312.43.camel@localhost>
> After I upgraded the server from 2.4.14 to 2.4.20, I am having a problem
> mounting and unmounting the NFS partitions using autofs. I have all
> of the clients touch the nfs filesystems (ls /misc/scratchx) to cause
> them to mount. Many of the mounts fail (~ 50%) with the error.
Dave,
You might want to have Craig mention how many clients are involved.
If this is the FSL cluster, it's 1000. I don't know how mount decides
whether to use UCP or TCP for the mount operation, but I do know that
1000 UDP requests heading at the same server at the same time is some
major congestion. 1000 TCP connections against the same server is
likewise problemmatic.
-- greg
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache
Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-01-16 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 19:17 NFS mount/umount problem David B. Ritch
2003-01-16 20:00 ` Greg Lindahl [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 22:00 Heflin, Roger A.
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=20030116200018.GA1253@wumpus.internal.keyresearch.com \
--to=lindahl@keyresearch.com \
--cc=ctierney@hpti.com \
--cc=dritch@hpti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.