From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jason Keltz <jas@cse.yorku.ca>
Cc: linux-nfs@vger.kernel.org
Subject: Re: hang on existing systems when exporting NFS share to new systems
Date: Wed, 28 Jul 2010 13:42:41 -0400 [thread overview]
Message-ID: <20100728174241.GB19362@fieldses.org> (raw)
In-Reply-To: <4C503450.1010609@cse.yorku.ca>
On Wed, Jul 28, 2010 at 09:44:48AM -0400, Jason Keltz wrote:
> Hi.
>
> My list of NFS exports has been gradually growing over the years.
> Right now, for example, my home directories are exported to around
> 800 hosts. (although only a relatively small subset of those will
> mount at the same time...). I used to just add hosts to
> /etc/exports on the file server, and run "exportfs -r", and
> everything would be fine. New systems would be able to mount
> everything perfectly, and existing systems would not be affected at
> all. As the list has grown, I've been noticing a problem. Now, when
> I run exportfs -r, there is an approximate 7-10 second hang on the
> systems that have already mounted the share, and then everything
> returns to normal. This doesn't happen *while* exportfs -r is
> running, but just after it exits. I figured that maybe exportfs was
> "unexporting"/re-exporting to hosts that already had the share in
> use which might have caused the problem, so I tried to manually
> add/remove hosts thinking that this would only affect those hosts,
> but it did not. Exporting to one new host still causes the hang on
> all existing hosts.
>
> Since I have multiple exports to all of the hosts, adding one new
> host can hang things for a while. I can see that reducing the list
> of exports, or hosts would reduce the delay. What I am wondering is
> if there is a better way that I can add hosts without affecting
> connectivity to existing hosts?
>
> The NFS server itself is pretty powerful -- dual quad core box, lots
> of memory, many NFS threads, exclusive NFS server, etc... I am
> running an older RHEL4 release though, so it would have an older
> kernel/NFS system. Maybe this issue has been solved in newer
> releases.
There have been fixes in this area, though I don't see any that I'm sure
would address your problem. If you could test with the latest nfs-utils
(ideally, with the latest nfs-utils and kernel) and let us know the
result, that would be helpful.
The -t option to rpc.mountd (may need a newer nfs-utils?) may also help.
Also worth filing an RHEL bug.
--b.
next prev parent reply other threads:[~2010-07-28 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 13:44 hang on existing systems when exporting NFS share to new systems Jason Keltz
2010-07-28 17:42 ` J. Bruce Fields [this message]
2010-07-31 2:07 ` Jason Keltz
[not found] ` <4C53855F.5060201-Au2wK/vbkGRbjDw2KniTvg@public.gmane.org>
2010-10-03 21:13 ` J. Bruce Fields
2010-10-04 13:21 ` Jason Keltz
[not found] ` <4CA9D4BC.1060201-Au2wK/vbkGRbjDw2KniTvg@public.gmane.org>
2010-10-04 15:52 ` J. Bruce Fields
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=20100728174241.GB19362@fieldses.org \
--to=bfields@fieldses.org \
--cc=jas@cse.yorku.ca \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).