Bug 63994 - exceeding maximum nfs mounts
Summary: exceeding maximum nfs mounts
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: autofs
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-23 14:07 UTC by Need Real Name
Modified: 2007-04-18 16:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-01 18:13:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2002-04-23 14:07:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)

Description of problem:
when the number of nfs mounts gets too large(usually 256) we get this 
message: "mount table full".
Is there a way to increase the number of nfs mounts?


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.easy to reproduce just by doing a whole bunch of mounts from remote machines


Steps to Reproduce:
1. use a loop to do lots of mounts from another server
2. check after each mount how many mounts
3. eventually get  "mount table full".

	

Actual Results:  "mount table full", won't do any futher mounts, and we think 
automount gets confused and won't unmount when quiet.

Expected Results:  automount should have nfs mounted other users' home 
directories
from other machines, but it can't until some of the currents mounts are 
unmounted.

Additional info:

we think that this might be a configarable limit that can be set in /proc, but 
where?

Comment 1 James Pearson 2002-04-26 09:08:47 UTC
There was a post recently on the linux-nfs and linux-kernel mail lists  - see:

http://marc.theaimsgroup.com/?l=linux-nfs&m=101976679701722&w=2

Which I _think_ relates to your problem ...

Comment 2 Steve Dickson 2004-09-01 18:13:04 UTC
I believe we do a better job in later kernels. Please
try the Fedora Core kernels and reopen if necessary


Note You need to log in before you can comment on or make changes to this bug.