Re: auotfs v4

[Greg Bradner <gregb@rhythm.com>]

It does seem to be a problem with /proc/mounts. But I can't tell if it 
can't umount or if it's trying to mount the same location.  How can I tell?

Oren Held wrote:

>Hi,
>
>check your /proc/mounts file when it happens.
>As you were already told it happens because of more than 256 nfs mounts
>- but the question is wether you really have to mount that many (then
>you have a problem, but there must be some patches to fix it) - or
>whether it's an automounter problem.. I myself experienced such a thing
>that tried to mount the same location many times till it filled the
>whole mount table.
>
> - Oren
>
>On Thu, 2003-11-06 at 20:11, Greg Bradner wrote:
>  
>
>>Any ideas what 'mount table full' means?
>>Nov  6 10:08:44 linn automount[27555]: >> NFSv3 not supported!
>>Nov  6 10:08:44 linn automount[27555]: >> mount table full
>>Nov  6 10:08:44 linn automount[27555]: mount(nfs): nfs: mount failure 
>>fs7:/vol/vol0/systems/celia/utils on /celia/utils/
>>Nov  6 10:09:15 linn automount[1899]: attempting to mount entry 
>>/misc/hsm_cache
>>Nov  6 10:09:15 linn automount[27589]: >> NFSv3 not supported!
>>Nov  6 10:09:15 linn automount[27589]: >> mount table full
>>Nov  6 10:09:15 linn automount[27589]: mount(nfs): nfs: mount failure 
>>fs8:/vol/vol0/hsm_cache on /misc/hsm_cache/
>>
>>Everything works fine after a reboot.
>>    
>>

-- 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rhythm & Hues
5404 Jandy Place
Los Angeles, CA 90066
Voice: 310 448-7763
Fax:   310 448-7600
gregb@rhythm.com