From: Mike Waychison <michael.waychison@sun.com>
To: Greg Bradner <gregb@rhythm.com>
Cc: autofs@linux.kernel.org
Subject: Re: auotfs v4
Date: Thu, 06 Nov 2003 15:25:41 -0500 [thread overview]
Message-ID: <3FAAAE45.7030702@sun.com> (raw)
In-Reply-To: <3FAA8EE3.1060109@rhythm.com>
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2003-11-06 20:25 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 [this message]
2003-11-06 22:57 ` Oren Held
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=3FAAAE45.7030702@sun.com \
--to=michael.waychison@sun.com \
--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.