* Re: auotfs v4 [not found] <Pine.LNX.4.44.0311070711380.2959-100000@raven.themaw.net> @ 2003-11-07 14:47 ` Greg Bradner 2003-11-14 14:29 ` Greg Bradner 0 siblings, 1 reply; 7+ messages in thread From: Greg Bradner @ 2003-11-07 14:47 UTC (permalink / raw) To: autofs [-- 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: auotfs v4 2003-11-07 14:47 ` auotfs v4 Greg Bradner @ 2003-11-14 14:29 ` Greg Bradner 2003-11-14 16:08 ` Greg Bradner 0 siblings, 1 reply; 7+ messages in thread From: Greg Bradner @ 2003-11-14 14:29 UTC (permalink / raw) To: autofs [-- 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: auotfs v4 2003-11-14 14:29 ` Greg Bradner @ 2003-11-14 16:08 ` Greg Bradner 0 siblings, 0 replies; 7+ messages in thread From: Greg Bradner @ 2003-11-14 16:08 UTC (permalink / raw) To: autofs [-- 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* auotfs v4 @ 2003-11-06 18:11 Greg Bradner 2003-11-06 20:25 ` Mike Waychison 2003-11-06 22:57 ` Oren Held 0 siblings, 2 replies; 7+ messages in thread From: Greg Bradner @ 2003-11-06 18:11 UTC (permalink / raw) To: autofs 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: auotfs v4 2003-11-06 18:11 Greg Bradner @ 2003-11-06 20:25 ` Mike Waychison 2003-11-06 22:57 ` Oren Held 1 sibling, 0 replies; 7+ messages in thread From: Mike Waychison @ 2003-11-06 20:25 UTC (permalink / raw) To: Greg Bradner; +Cc: autofs 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. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: auotfs v4 2003-11-06 18:11 Greg Bradner 2003-11-06 20:25 ` Mike Waychison @ 2003-11-06 22:57 ` Oren Held 2003-11-07 14:40 ` Greg Bradner 1 sibling, 1 reply; 7+ messages in thread From: Oren Held @ 2003-11-06 22:57 UTC (permalink / raw) To: Greg Bradner; +Cc: autofs 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. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: auotfs v4 2003-11-06 22:57 ` Oren Held @ 2003-11-07 14:40 ` Greg Bradner 0 siblings, 0 replies; 7+ messages in thread From: Greg Bradner @ 2003-11-07 14:40 UTC (permalink / raw) To: autofs 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2003-11-14 16:08 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <Pine.LNX.4.44.0311070711380.2959-100000@raven.themaw.net>
2003-11-07 14:47 ` auotfs v4 Greg Bradner
2003-11-14 14:29 ` Greg Bradner
2003-11-14 16:08 ` Greg Bradner
2003-11-06 18:11 Greg Bradner
2003-11-06 20:25 ` Mike Waychison
2003-11-06 22:57 ` Oren Held
2003-11-07 14:40 ` Greg Bradner
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.