From: Oren Held <oren@held.org.il>
To: Greg Bradner <gregb@rhythm.com>
Cc: autofs@linux.kernel.org
Subject: Re: auotfs v4
Date: Fri, 07 Nov 2003 00:57:47 +0200 [thread overview]
Message-ID: <1068159466.10397.4.camel@localhost> (raw)
In-Reply-To: <3FAA8EE3.1060109@rhythm.com>
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.
next prev parent reply other threads:[~2003-11-06 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 18:11 auotfs v4 Greg Bradner
2003-11-06 20:25 ` Mike Waychison
2003-11-06 22:57 ` Oren Held [this message]
2003-11-07 14:40 ` Greg Bradner
[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
2003-11-14 16:08 ` 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=1068159466.10397.4.camel@localhost \
--to=oren@held.org.il \
--cc=autofs@linux.kernel.org \
--cc=gregb@rhythm.com \
/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.