All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Fletcher Mattox <fletcher@cs.utexas.edu>
Cc: autofs@linux.kernel.org
Subject: Re: autofs illustrations
Date: Wed, 08 Nov 2006 08:29:30 -0500	[thread overview]
Message-ID: <4551DBBA.40004@redhat.com> (raw)
In-Reply-To: <200611072124.kA7LOTES005928@cs.utexas.edu>

Fletcher Mattox wrote:
>> Fletcher Mattox wrote:
>> ...
>>     
>>> Unprivileged ports and/or UDP are not viable options for us, so I am
>>> forced to increase the timeout from 5 minutes to 24 hours, which in
>>> practice means they are always mounted.  We have about 400 automounted
>>> filesystems, so the only long term solution for us is to try to coalesce
>>> them to less than 100.  Very painful.
>>>       
>> You have 400 automounted file systems, all of which need to be mounted at
>> the same time?  
>>     
>
> Not all of them, but certainly more than 100 of them, which seems to
> be the limit we are talking about. 
>
>   

Hmm.  Perhaps Chuck Lever's work to reduce the number of required TCP
connections would help in this sort of deployment.

>> If so, I might suggest that static mounts might better serve
>> your needs.  
>>     
>
> Really?  I think this is the first time I have ever heard someone
> advocate static mounts as a solution to a large number of filesystems
> (especially ones that tend to appear and disappear frequently).
> But you are right, and this is effectively the solution we arrived at
> by increasing the timeout.
>
>   

Well, if the file systems tend to get mounted and then stay mounted,
then automounting does little good and can be harmful.

Automounting also does not tend to work well with large numbers of
file systems and not always for the scalability reasons which are
being seen here.
>> Or, rethink the application and deployment.
>>     
>
> I think that's what said in my penultimate sentence. :)

Yup...  :-)

       ps

  reply	other threads:[~2006-11-08 13:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 22:37 autofs illustrations wengang wang
2006-11-07  0:10 ` Jeff Moyer
2006-11-07 17:19   ` Fletcher Mattox
2006-11-07 20:40     ` Peter Staubach
2006-11-07 21:24       ` Fletcher Mattox
2006-11-08 13:29         ` Peter Staubach [this message]
2006-11-08 16:38           ` Jeff Moyer
2006-11-08 15:32       ` Michael Blandford
2006-11-08  3:59     ` Ian Kent
2006-11-08 13:25       ` Peter Staubach
2006-11-08 14:00         ` Ian Kent
2006-11-08 22:34           ` Joe Pruett
2006-11-08 23:03             ` Jeff Moyer
2006-11-09  0:37               ` Peter Staubach

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=4551DBBA.40004@redhat.com \
    --to=staubach@redhat.com \
    --cc=autofs@linux.kernel.org \
    --cc=fletcher@cs.utexas.edu \
    /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.