From: Greg Bradner <gregb@rhythm.com>
To: autofs@linux.kernel.org
Subject: Re: auotfs v4
Date: Fri, 07 Nov 2003 06:47:18 -0800 [thread overview]
Message-ID: <3FABB076.5080702@rhythm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0311070711380.2959-100000@raven.themaw.net>
[-- 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
next parent reply other threads:[~2003-11-07 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0311070711380.2959-100000@raven.themaw.net>
2003-11-07 14:47 ` Greg Bradner [this message]
2003-11-14 14:29 ` auotfs v4 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
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=3FABB076.5080702@rhythm.com \
--to=gregb@rhythm.com \
--cc=autofs@linux.kernel.org \
/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 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.