From: Mike Waychison <Michael.Waychison@Sun.COM>
To: "Ogden, Aaron A." <aogden@unocal.com>
Cc: autofs mailing list <autofs@linux.kernel.org>,
Ian Kent <raven@themaw.net>
Subject: Re: multiple servers per automount
Date: Thu, 09 Oct 2003 15:00:14 -0400 [thread overview]
Message-ID: <3F85B03E.2050109@sun.com> (raw)
In-Reply-To: <6AB920CC10586340BE1674976E0A991D5955F1@slexch2.sugarland.unocal.com>
Ogden, Aaron A. wrote:
>Ouch. As you may know, the limit is *much* lower in linux. Something
>that I've been struggling with recently...
>
>Under normal circumstances I would not be concerned with 'limitations'
>of a few hundred active NFS mounts, but such limitations certainly limit
>scalability for the extreme cases.
>
>
The maximum number of plain pseudo-block device filesystems on a given
filesystem is limitted to 256. (This includes proc, autofs, nfs..).
This is because pseudo-block filesystems all use major 0, and each have
a different minor (thus the 256 limit).
There are however patches floating around (look at SuSe's kernels, I'm
not sure about RH) that allow n majors to be used (default 5). This
gives you 1280 mounts, a big step up :)
Mike Waychison
next prev parent reply other threads:[~2003-10-09 19:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 18:45 multiple servers per automount Ogden, Aaron A.
2003-10-09 19:00 ` Mike Waychison [this message]
2003-10-10 1:08 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2003-10-10 15:16 Ogden, Aaron A.
2003-10-09 22:07 Ogden, Aaron A.
2003-10-09 21:20 Ogden, Aaron A.
2003-10-09 21:36 ` Mike Waychison
2003-10-10 1:16 ` Ian Kent
2003-10-10 1:15 ` Ian Kent
2003-10-08 17:24 Rich Sahlender
2003-10-08 18:57 ` H. Peter Anvin
2003-10-08 20:43 ` Rich Sahlender
2003-10-08 21:28 ` Mike Waychison
2003-10-09 3:07 ` Ian Kent
2003-10-09 18:23 ` Mike Waychison
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=3F85B03E.2050109@sun.com \
--to=michael.waychison@sun.com \
--cc=aogden@unocal.com \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/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.