From: Matt Schillinger <mschilli@vss.fsi.com>
To: Steve Dickson <SteveD@RedHat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: exportfs operations hang
Date: 18 Jun 2003 11:47:46 -0500 [thread overview]
Message-ID: <1055954867.13314.8.camel@mosix> (raw)
In-Reply-To: <3EEF914A.8030000@RedHat.com>
On Tue, 2003-06-17 at 17:08, Steve Dickson wrote:
> Here does strace say its hanging?
>
> SteveD.
Duh! No I haven't.. I will do that when issues occur again.. However, I
may or may not have found the problem..
A few new things that I've found.
rpc.mountd is not displaying any syslog entries when hangs occur on
clients.. the client gets 'Permission Denied' when trying to mount (via
automount). Other clients are accessing the mounts just fine..
I found that there is a -o or --descriptor option for file descriptors,
which the default operation is 256 file descriptors. This got me
thinking about how many file descriptors that I should have.. I couldn't
find anything about tuning file descriptors for rpc.mountd. Could
someone give me a guideline or idea?
I went ahead and bumped the file descriptors up to 512 for good measure.
( this required a kill of the current rpc.mountd and restart of it.)
After the restart, the clients that were getting 'Permission Denied',
were able to access the mounts. I do not know yet if the restart fixed
the problem, or the increased file descriptors, or both.
I would really like to know what the recommended file descriptor number
should be.
Default is 256, but the default nfsd threads is 8.
I am running 64 threads, with an Input Queue of 2097152
Should rpc.mountd file descriptors move up in relation to number of
threads?
Thanks for your help,
Matt Schillinger
mschilli@vss.fsi.com
>
> Matt Schillinger wrote:
>
> >Hello,
> >
> >I am having reproducible problems with exportfs.
> >
> >When I try to run exportfs or exportfs -u, it simply stalls and never
> >drops back to commandline.. if i CTRL+C, i see that (in the case of an
> >exportfs) the mountpoint is still not shared. In the case of an exportfs
> >-u, If i CTRL+C it, the mountpoint IS still shared. I do not know what
> >is causing the problem.. the only workaround that I have found is to
> >restart nfsd.. Is there something in rmtab/xtab/etab that could cause an
> >exportfs hangup?
> >
> >I am using 64 threads, and am having no thread utilization issues
> >according to /proc/net/rpc/nfsd
> >
> >Has anyone else had this problem?
> >
> >Thanks for your help
> >
> >
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-06-18 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 19:46 exportfs operations hang Matt Schillinger
2003-06-17 22:08 ` Steve Dickson
2003-06-18 16:47 ` Matt Schillinger [this message]
2003-07-03 14:57 ` Matt Schillinger
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=1055954867.13314.8.camel@mosix \
--to=mschilli@vss.fsi.com \
--cc=SteveD@RedHat.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.