All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ogden, Aaron A." <aogden@unocal.com>
To: Ian Kent <raven@themaw.net>, Mike Waychison <Michael.Waychison@Sun.COM>
Cc: autofs mailing list <autofs@linux.kernel.org>, nfs@lists.sourceforge.net
Subject: RE: multiple servers per automount
Date: Fri, 10 Oct 2003 10:16:01 -0500	[thread overview]
Message-ID: <6AB920CC10586340BE1674976E0A991D5955FC@slexch2.sugarland.unocal.com> (raw)



-----Original Message-----
From: Ian Kent [mailto:raven@themaw.net] 
Sent: Thursday, October 09, 2003 8:09 PM
To: Mike Waychison
Cc: Ogden, Aaron A.; autofs mailing list; nfs@lists.sourceforge.net
Subject: Re: [autofs] multiple servers per automount

>> 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 :)
>>
>
> But as Aaron and I know things go pear shaped at just shy of 800
mounts
> with RedHat kernels. They have the more-unnamed patch.
>
> So this would indicate that even if there is a device system that can
> increase the number of unnamed devices that subsystems like NFS cannot
> handle this many mounts.

Maybe.  I'm not 100% certain though.  Currently I am holding steady at
710 active mounts, I am going to write a little script to mount more in
small increments, ie. read a list of ~1000 mountpoints from /home, mount
a few of them, check the filesystems, and repeat... this way I will know
exactly where things break down.

             reply	other threads:[~2003-10-10 15:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 15:16 Ogden, Aaron A. [this message]
2003-10-13  3:23 ` [NFS] RE: multiple servers per automount Ian Kent
2003-10-14  7:05   ` Joseph V Moss
2003-10-14 13:37     ` RE: [autofs] " Ian Kent
2003-10-14 13:37       ` Ian Kent
2003-10-14 15:52       ` [NFS] " Mike Waychison
2003-10-14 15:52         ` [NFS] " Mike Waychison
2003-10-14 20:44         ` [NFS] RE: [autofs] " H. Peter Anvin
2003-10-14 23:12           ` Mike Waychison
2003-10-15 10:28             ` Ingo Oeser
2003-10-15 16:16               ` Mike Waychison
2003-10-23 13:37               ` Ian Kent
2003-10-23 17:00                 ` Mike Waychison
2003-10-23 17:09                   ` Tim Hockin
2003-10-24  0:47                   ` Ian Kent
2003-10-24  1:42                     ` Tim Hockin
2003-10-15  7:22         ` Ian Kent
2003-10-15  7:22           ` Ian Kent
2003-10-15  7:22           ` Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
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-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=6AB920CC10586340BE1674976E0A991D5955FC@slexch2.sugarland.unocal.com \
    --to=aogden@unocal.com \
    --cc=Michael.Waychison@Sun.COM \
    --cc=autofs@linux.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --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.