From: "Marion, Mike" <mmarion@qualcomm.com>
To: Ian Kent <raven@themaw.net>
Cc: Autofs <autofs@vger.kernel.org>
Subject: Re: documentation issues
Date: Wed, 13 Jul 2016 02:17:42 +0000 [thread overview]
Message-ID: <20160713021741.GJ18749@qualcomm.com> (raw)
In-Reply-To: <1468246190.3102.121.camel@themaw.net>
On Mon, Jul 11, 2016 at 10:09:50PM +0800, Ian Kent wrote:
> What is needed is a re-write of the user space <-> kernel space communication
> essentially to add readdir functionality.
>
> So that listing a directory would show the possible map mount points without the
> need to create the mount point directories.
Oh my god.. we need this!
We have huge direct maps here and with the changing of /etc/mtab to a
link to /proc/self/mounts things have gotten horrible. We've worked
with suse to help speed up the start of autofs (it was taking 6+ hours
to simply start the first time due to how automount reads the mtab file,
stats paths, does the mkdir, etc). But things like mkinitrd running
with our huge maps loaded can take 20-30 min due to all the parsing
different steps do for various filesystem checks. I've learned to stop
automount and do a full umount -t autofs -a before running something
like a zypper update with a kernel upgrade.
--
Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com
Brian: "So enlighten us, what's your idea of the perfect man?"
Helen: "Oh, I don't know... Solid, sensitive and dependable, but with a sense of
whimsy, a love of music and children. A sense of commitment but a respect for my
independence; adventurous yet a homebody... I really hadn't thought about it that
much." Joe: "Sounds great Helen, but Kermit is a frog." => Wings--
To unsubscribe from this list: send the line "unsubscribe autofs" in
prev parent reply other threads:[~2016-07-13 2:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 21:17 documentation issues Xen
2016-07-06 0:57 ` Ian Kent
2016-07-06 4:47 ` Xen
2016-07-06 12:48 ` Ian Kent
2016-07-06 12:53 ` Erwan Loaec
2016-07-10 17:07 ` Xen
2016-07-11 14:09 ` Ian Kent
2016-07-13 2:17 ` Marion, Mike [this message]
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=20160713021741.GJ18749@qualcomm.com \
--to=mmarion@qualcomm.com \
--cc=autofs@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).