From: Dannie Stanley <dannie.stanley@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: autofs timeout and large map
Date: Fri, 28 Oct 2005 15:28:05 -0500 [thread overview]
Message-ID: <89e9feae0510281328hac26b2ct22bb466ee5a51d36@mail.gmail.com> (raw)
I think I may have discovered a bug. But perhaps I overlooked
something -- looking for advice.
I have generated a DIRECT map file and defined it in /etc/auto.master.
My direct mappings look like this (located in /etc/auto.virtual):
/virtual/USERNAME \
/public --bind 127.0.0.1:/usr/local/files/public \
/private --bind 127.0.0.1:/usr/local/files/USERNAME
My /etc/auto.virtual file has 1345 entries very similar to the example
provided (not wrapped like the example above). Everything works like
expected for the first mount. When the mount timeout expires, the
mount will not auto remount. When I try to `ls`, it gives the error:
"No such file or directory"
When --ghost is enabled most directories look like this when autofs
first starts:
drwxrwxr-x 2 virtual virtual 4096 Oct 28 14:45 private
However after the timeout they look like this:
dr-xr-xr-x 2 root root 0 Oct 28 14:45 private
Once I restart autofs it mounts again fine the first time. For now I
have set my timeout to 24 hours which functions as a work-around but
clutters up my mounted filesystems.
My system is in production and I can't recreate the problem right now
lest I interrupt users. I have done my best to recreate the actual
directory listings and error messages that I saw but they may not 100%
accurate as they are from memory.
Thanks for any advice,
Dannie
--
Dannie M. Stanley
"The Feynman Problem-Solving Algorithm: (1) write down the problem;
(2) think very hard; (3) write down the answer." - Murray Gell-Mann
reply other threads:[~2005-10-28 20:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=89e9feae0510281328hac26b2ct22bb466ee5a51d36@mail.gmail.com \
--to=dannie.stanley@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®