auotfs v4

auotfs v4

[Greg Bradner]

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

Re: auotfs v4

[Mike Waychison]

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.
>
It means that you have more than 256 mounts that don't have a 
block-device back-end.  These include NFS, autofs, procfs, sysfs...

This is a known limitation in linux 2.4.  You may want to try a patch 
like the following:

http://people.redhat.com/zaitcev/linux/linux-2.4.19-pre7-unmaj.diff

-- 
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
mailto: Michael.Waychison@Sun.COM
http://www.sun.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE:  The opinions expressed in this email are held by me, 
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 

Re: auotfs v4

[Oren Held]

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.

Re: auotfs v4

[Greg Bradner]

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

Re: auotfs v4

[Greg Bradner]

[-- Attachment #1.1: Type: text/plain, Size: 2450 bytes --]

I am using RH 7.3 with the 2.4.20 kernel. It doen't have the patch. But 
I don't need it at the moment. I need to figure out why my /proc/mounts 
file is filling up with the same mount points.

My problem is a NetApp. Not because it's a NetApp, rather I believe it's 
the way volumes are exported.
 > showmount -e fs7
Export list for fs7:
/vol/vol0/systems   (everyone)
/vol/vol0/muse      (everyone)
/vol/vol0/avidcache (everyone)
/vol/vol0           (everyone)

What I see in /proc/mounts:
fs7:/vol/vol0/muse /nfs/hosts3/fs7/vol/vol0/muse nfs 
rw,v2,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=fs7 0 0
fs7:/vol/vol0/avidcache /nfs/hosts3/fs7/vol/vol0/avidcache nfs 
rw,v2,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=fs7 0 0
fs7:/vol/vol0/systems /nfs/hosts3/fs7/vol/vol0/systems nfs 
rw,v2,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=fs7 0 0

But I don't see:
/vol/vol0

I believe autofs is expiring and unmounting fs7:/vol/vol0 and getting 
confused as what to do with the directories under that root vol.


Ian Kent wrote:

>On Thu, 6 Nov 2003, Mike Waychison wrote:
>
>  
>
>>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.
>>>
>>>      
>>>
>>It means that you have more than 256 mounts that don't have a 
>>block-device back-end.  These include NFS, autofs, procfs, sysfs...
>>
>>This is a known limitation in linux 2.4.  You may want to try a patch 
>>like the following:
>>
>>http://people.redhat.com/zaitcev/linux/linux-2.4.19-pre7-unmaj.diff
>>
>>
>>    
>>
>
>Most of the RedHat packaged kernels have this patch.
>
>What distro are you using?
>What version of autofs?
> 
>  
>

-- 

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


[-- Attachment #1.2: Type: text/html, Size: 3331 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs

Re: auotfs v4

[Greg Bradner]

[-- Attachment #1.1: Type: text/plain, Size: 3080 bytes --]

This remains a major problem for me. I have changed the exports file on 
the NetApp, but am still having the same problem.
Why would /nfs/hosts3/fs7/vol/vo0 get umount but not exported 
directories under that mount point?  Why does /etc/mtab reflect an 
umount but /proc/mounts show them mounted?

Any ideas?

Greg Bradner wrote:

> I am using RH 7.3 with the 2.4.20 kernel. It doen't have the patch. 
> But I don't need it at the moment. I need to figure out why my 
> /proc/mounts file is filling up with the same mount points.
>
> My problem is a NetApp. Not because it's a NetApp, rather I believe 
> it's the way volumes are exported.
> > showmount -e fs7
> Export list for fs7:
> /vol/vol0/systems   (everyone)
> /vol/vol0/muse      (everyone)
> /vol/vol0/avidcache (everyone)
> /vol/vol0           (everyone)
>
> What I see in /proc/mounts:
> fs7:/vol/vol0/muse /nfs/hosts3/fs7/vol/vol0/muse nfs 
> rw,v2,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=fs7 0 0
> fs7:/vol/vol0/avidcache /nfs/hosts3/fs7/vol/vol0/avidcache nfs 
> rw,v2,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=fs7 0 0
> fs7:/vol/vol0/systems /nfs/hosts3/fs7/vol/vol0/systems nfs 
> rw,v2,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=fs7 0 0
>
> But I don't see:
> /vol/vol0
>
> I believe autofs is expiring and unmounting fs7:/vol/vol0 and getting 
> confused as what to do with the directories under that root vol.
>
>
> Ian Kent wrote:
>
>>On Thu, 6 Nov 2003, Mike Waychison wrote:
>>
>>  
>>
>>>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.
>>>>
>>>>      
>>>>
>>>It means that you have more than 256 mounts that don't have a 
>>>block-device back-end.  These include NFS, autofs, procfs, sysfs...
>>>
>>>This is a known limitation in linux 2.4.  You may want to try a patch 
>>>like the following:
>>>
>>>http://people.redhat.com/zaitcev/linux/linux-2.4.19-pre7-unmaj.diff
>>>
>>>
>>>    
>>>
>>
>>Most of the RedHat packaged kernels have this patch.
>>
>>What distro are you using?
>>What version of autofs?
>> 
>>  
>>
>
>-- 
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Rhythm & Hues
>5404 Jandy Place
>Los Angeles, CA 90066
>Voice: 310 448-7763
>Fax:   310 448-7600
>gregb@rhythm.com
>  
>

-- 

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


[-- Attachment #1.2: Type: text/html, Size: 4190 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs

Re: auotfs v4

[Greg Bradner]

[-- Attachment #1.1: Type: text/plain, Size: 3544 bytes --]

Partial expiry? What does that mean?

Nov 14 08:02:40 lid2 automount[19594]: failed to recover from partial 
expiry of /nfs/hosts3/fs7


Greg Bradner wrote:

> This remains a major problem for me. I have changed the exports file 
> on the NetApp, but am still having the same problem.
> Why would /nfs/hosts3/fs7/vol/vo0 get umount but not exported 
> directories under that mount point?  Why does /etc/mtab reflect an 
> umount but /proc/mounts show them mounted?
>
> Any ideas?
>
> Greg Bradner wrote:
>
>> I am using RH 7.3 with the 2.4.20 kernel. It doen't have the patch. 
>> But I don't need it at the moment. I need to figure out why my 
>> /proc/mounts file is filling up with the same mount points.
>>
>> My problem is a NetApp. Not because it's a NetApp, rather I believe 
>> it's the way volumes are exported.
>> > showmount -e fs7
>> Export list for fs7:
>> /vol/vol0/systems   (everyone)
>> /vol/vol0/muse      (everyone)
>> /vol/vol0/avidcache (everyone)
>> /vol/vol0           (everyone)
>>
>> What I see in /proc/mounts:
>> fs7:/vol/vol0/muse /nfs/hosts3/fs7/vol/vol0/muse nfs 
>> rw,v2,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=fs7 0 0
>> fs7:/vol/vol0/avidcache /nfs/hosts3/fs7/vol/vol0/avidcache nfs 
>> rw,v2,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=fs7 0 0
>> fs7:/vol/vol0/systems /nfs/hosts3/fs7/vol/vol0/systems nfs 
>> rw,v2,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=fs7 0 0
>>
>> But I don't see:
>> /vol/vol0
>>
>> I believe autofs is expiring and unmounting fs7:/vol/vol0 and getting 
>> confused as what to do with the directories under that root vol.
>>
>>
>> Ian Kent wrote:
>>
>>>On Thu, 6 Nov 2003, Mike Waychison wrote:
>>>
>>>  
>>>
>>>>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.
>>>>>
>>>>>      
>>>>>
>>>>It means that you have more than 256 mounts that don't have a 
>>>>block-device back-end.  These include NFS, autofs, procfs, sysfs...
>>>>
>>>>This is a known limitation in linux 2.4.  You may want to try a patch 
>>>>like the following:
>>>>
>>>>http://people.redhat.com/zaitcev/linux/linux-2.4.19-pre7-unmaj.diff
>>>>
>>>>
>>>>    
>>>>
>>>
>>>Most of the RedHat packaged kernels have this patch.
>>>
>>>What distro are you using?
>>>What version of autofs?
>>> 
>>>  
>>>
>>
>>-- 
>>
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>Rhythm & Hues
>>5404 Jandy Place
>>Los Angeles, CA 90066
>>Voice: 310 448-7763
>>Fax:   310 448-7600
>>gregb@rhythm.com
>>  
>>
>
>-- 
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Rhythm & Hues
>5404 Jandy Place
>Los Angeles, CA 90066
>Voice: 310 448-7763
>Fax:   310 448-7600
>gregb@rhythm.com
>  
>

-- 

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


[-- Attachment #1.2: Type: text/html, Size: 4888 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs