All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Thomas Chan <tchan@ilm.com>
Cc: autofs@linux.kernel.org
Subject: Re: autofs stops working after a while with USE_MISC_DEVICE
Date: Fri, 03 Jul 2009 16:41:47 +0800	[thread overview]
Message-ID: <4A4DC44B.6040709@themaw.net> (raw)
In-Reply-To: <alpine.LRH.2.00.0907022222180.2710@talon.lucasfilm.com>

Thomas Chan wrote:
> 
>>> lsof shows that automount has 10288 files open, of which most of these
>>> are like:
>>>
>>> automount 15539      root *217u     sock                0,4 595374 can't
>>> identify protocol
>>> automount 15539      root *218u     sock                0,4 595376 can't
>>> identify protocol
>>> automount 15539      root *219u     sock                0,4 595378 can't
>>> identify protocol
>>> automount 15539      root *220u     sock                0,4 595380 can't
>>> identify protocol
>>>
>>> Upon restarting autofs, these open files are cleared out and automount
>>> works, but the open files gradually build up again.
>>>
>>> After setting USE_MISC_DEVICE=no, I no longer get the open file issue,
>>> but we are trying to remedy the autofs lazy unmount / cwd issue.
>>
>> Mmm .. that's not good.
>> I'll have a look and see what I can see.
>>
>> Ian
> 
> Sorry about the initial red herring, but it looks like I'm getting the
> increasing open files even with USE_MISC_DEVICE=no.  I must have
> previously done a grep for autofs instead of automount.
> 
> In any case, after a restart of autofs:
> [root@talon ~]# /etc/init.d/autofs restart
> Stopping automount:                                        [  OK  ]
> Starting automount:                                        [  OK  ]
> [root@talon ~]# lsof |grep automount | grep sock
> automount   309      root   52u     sock                0,4 3230868911
> can't identify protocol
> automount   309      root   54u     sock                0,4 3230868918
> can't identify protocol
> automount   309      root   55u     sock                0,4 3230868920
> can't identify protocol
> automount   309      root   56u     sock                0,4 3230868922
> can't identify protocol
> automount   309      root   57u     sock                0,4 3230868924
> can't identify protocol
> automount   309      root   59u     sock                0,4 3230868930
> can't identify protocol
> automount   309      root   61u     sock                0,4 3230868937
> can't identify protocol
> automount   309      root   62u     sock                0,4 3230868939
> can't identify protocol
> automount   309      root   63u     sock                0,4 3230868941
> can't identify protocol
> automount   309      root   64u     sock                0,4 3230868943
> can't identify protocol
> automount   309      root   66u     sock                0,4 3230868949
> can't identify protocol
> automount   309      root   68u     sock                0,4 3230868956
> can't identify protocol
> automount   309      root   69u     sock                0,4 3230868958
> can't identify protocol
> automount   309      root   70u     sock                0,4 3230868960
> can't identify protocol
> automount   309      root   71u     sock                0,4 3230868962
> can't identify protocol
> automount   309      root   73u     sock                0,4 3230868968
> can't identify protocol
> automount   309      root   75u     sock                0,4 3230868975
> can't identify protocol
> automount   309      root   76u     sock                0,4 3230868977
> can't identify protocol
> automount   309      root   77u     sock                0,4 3230868979
> can't identify protocol
> automount   309      root   78u     sock                0,4 3230868981
> can't identify protocol
> [root@talon ~]#
> 
> This gradually increases with every new mount until automount has 10288
> files open.

What distribution, and more specifically, what libtirpc, if any?

Ian

  reply	other threads:[~2009-07-03  8:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 18:55 autofs stops working after a while with USE_MISC_DEVICE Thomas Chan
2009-07-03  4:40 ` Ian Kent
2009-07-03  5:35   ` Thomas Chan
2009-07-03  8:41     ` Ian Kent [this message]
2009-07-03 17:15       ` Thomas Chan
2009-07-04  3:49     ` Ian Kent
2009-07-04  4:32       ` Thomas Chan
2009-07-07 18:20         ` Thomas Chan
2009-07-08  1:04           ` 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=4A4DC44B.6040709@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=tchan@ilm.com \
    /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.