From: Johan van den Dorpe <johan.vandendorpe@framestore-cfc.com>
To: nfs@lists.sourceforge.net
Subject: Re: rpc.mountd stops functioning
Date: Thu, 25 Nov 2004 12:45:31 +0000 [thread overview]
Message-ID: <41A5D3EB.1000004@framestore-cfc.com> (raw)
In-Reply-To: <41122039.9040907@framestore-cfc.com>
I think I've got this sussed. After reading this thread:
http://sourceforge.net/mailarchive/message.php?msg_id=9891180
http://sourceforge.net/mailarchive/message.php?msg_id=9901077
I thought it might be worth testing the vanilla nfs-utils package from
kernel.org rather than the redhat supplied versions.
Now, I've had this setup running for 28 days without any issues on one
of our servers that has been a real problem in the past.
I'm going to try this solution on a wider scale to try and confirm this
further, but for now I consider this the fix.
My advice to anyone running a vanilla kernel is to run the vanilla
nfs-utils package and not a redhat nfs-utils package.
Johan van den Dorpe wrote:
> I clicked send a bit fast. Other info:
>
> Running RHEL 3 with 2.4.25 vanilla kernel. nfs-utils-1.0.5
>
> Experienced the problem in the past with Red Hat 7.3 with same 2.4.25
> kernel and 2.4.20 kernel + XFS patches + Trond's all patch for 2.4.20.
> Tried nfs-utils 0.3.3 and 1.0.6
>
> Johan van den Dorpe wrote:
>
>> Hello,
>>
>> For a long time we've been experiencing problems with rpc.mountd
>> stopping functioning.
>>
>> I'm finding it hard to pinpoint the precise circumstances where we
>> encounter a problem, but here is what we have observed:
>>
>> - A mount request, or a showmount -e, to the server will hang
>>
>> - The server will print a log message authenticating the mount request
>>
>> - The server doesn't print log messages that it has authenticated
>> unmount requests.
>>
>> - Killing rpc.mountd and then restarting it fixes the problem (I've
>> not tried a HUP)
>>
>> - There is a correlation between the number of mounts being handled
>> (i.e. the number of entries in rmtab) and the frequency of the problem.
>>
>> - The problem only occurs on servers that are mounted by a significant
>> number of hosts (500-700).
>>
>> - The more exports on the server, the more frequently the problem occurs.
>>
>> - It should be noted that clients are mounting subdirectories of a
>> single exported filesystem, so number of rmtab entries > number of
>> xtab entries.
>>
>> - Clearing the rmtab and restarting nfs (service nfs restart) seems to
>> provide the longest time between failures.
>>
>
>
--
Johan van den Dorpe
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-11-25 12:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 11:19 rpc.mountd stops functioning Johan van den Dorpe
2004-08-05 11:55 ` Johan van den Dorpe
2004-11-25 12:45 ` Johan van den Dorpe [this message]
2004-08-05 14:46 ` J. Bruce Fields
2004-08-11 10:02 ` Johan van den Dorpe
2004-08-19 15:26 ` Johan van den Dorpe
2004-08-27 3:31 ` Neil Brown
2004-08-27 23:16 ` J. Bruce Fields
2004-08-28 17:20 ` Garrick Staples
2004-08-30 5:54 ` Neil Brown
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=41A5D3EB.1000004@framestore-cfc.com \
--to=johan.vandendorpe@framestore-cfc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox