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 17:36:42 -0400 [thread overview]
Message-ID: <3F85D4EA.5030708@sun.com> (raw)
In-Reply-To: <6AB920CC10586340BE1674976E0A991D0C6B77@slexch2.sugarland.unocal.com>
Ogden, Aaron A. wrote:
>Yes, we are using the RH kernels as a base, the limit is supposed to be
>1200+ but my experiments have shown it to be just shy of 800. Or maybe
>that results is due to a bug in the autofs code.
>
I don't see how the autofs code would cause such a problem...
>I think the real
>solution to this problem is Richard Gooch's devfs and kernel 2.6. It's
>anyone's guess when there will be a distribution using both of those but
>I think Fedora might be the first.
>
2.6 mainline still has the 256 pseudo-block device limit. Fortunately,
the patches used in distros should still apply with minimal fuzz. Devfs
probably won't help matters here.
I think the next step in 2.6 is to change the bitmap used to grow as
needed.. especially now that minors are 20 bits, or 1048576 minors :))
Mike Waychison
next prev parent reply other threads:[~2003-10-09 21:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 21:20 multiple servers per automount Ogden, Aaron A.
2003-10-09 21:36 ` Mike Waychison [this message]
2003-10-10 1:16 ` Ian Kent
2003-10-10 1:15 ` Ian Kent
2003-10-10 1:15 ` [autofs] " 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 18:45 Ogden, Aaron A.
2003-10-09 19:00 ` Mike Waychison
2003-10-10 1:08 ` 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=3F85D4EA.5030708@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.