All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Loran <jonathan@loran.name>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: statfs() and autofs
Date: Sun, 20 Jul 2008 22:08:27 -0700	[thread overview]
Message-ID: <488419CB.6090108@loran.name> (raw)
In-Reply-To: <1216615194.3093.8.camel@raven.themaw.net>


[-- Attachment #1.1: Type: text/plain, Size: 1121 bytes --]



Ian Kent wrote:
> On Sun, 2008-07-20 at 20:41 -0700, Chris Walker wrote:
>   
>> From jimc [07/20 15:31]:
>>     
>>> Actually, only the sysop knows which is more important: doing the mount 
>>> storm to respond to stat() or statfs(), or avoiding the storm.
>>>       
>> Agreed. In our case, we have 'heavily discouraged' use of /net on our
>> big servers and we would prefer that statfs()/stat() waited for the
>> automount to complete.
>>     
>
> Just to be absolutely clear.
>
> The "browse" or "--ghost option isn't being used, in oder to avoid mount
> storms, but we still see stat(2) and statfs(2) (et. al.) not wait for a
> mount to complete.
>
> Is that right?
> Is anyone in a position to test a kernel patch?
>
>   
I may be willing to try the patch, but first I need to see if I can 
recreate the problem reliably.  If not, there isn't much use.  I just 
know that on our "faster" servers, the programmers I work with have 
demonstrated the issue.  I will need their help.  I'll let know if I 
make head way.  Thanks,

Jon

P.S. Chris, can you reliably demonstrate the not waiting for the mount 
problem?


[-- Attachment #1.2: Type: text/html, Size: 1657 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs

  parent reply	other threads:[~2008-07-21  5:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 20:48 statfs() and autofs Chris Walker
2008-07-16  3:43 ` Ian Kent
2008-07-16  5:21   ` Jonathan Loran
2008-07-20 22:24     ` Jim Carter
2008-07-21  3:41       ` Chris Walker
2008-07-21  4:39         ` Ian Kent
2008-07-21  4:56           ` Ian Kent
2008-07-21  5:00           ` Chris Walker
2008-07-21  5:12             ` Ian Kent
2008-07-21  5:08           ` Jonathan Loran [this message]
2008-07-21  5:50             ` Chris Walker
2008-07-21  7:35               ` Ian Kent
2008-07-22 16:39                 ` Chris Walker
2008-07-23 21:39                   ` Chris Walker
2008-08-04 17:17                   ` Chris Walker
2008-07-21 15:26           ` Steve Thompson
2008-07-16  5:30   ` Chris Walker
2008-07-16 14:05     ` Ian Kent

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=488419CB.6090108@loran.name \
    --to=jonathan@loran.name \
    --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.