From: Ian Kent <raven@themaw.net>
To: autofs@vger.kernel.org
Subject: Re: "rmdir_path: lstat of <path> failed" issues, despite updated autofs RPM
Date: Tue, 10 Nov 2015 16:48:04 +0800 [thread overview]
Message-ID: <1447145284.3028.8.camel@themaw.net> (raw)
In-Reply-To: <146CD18A-8C87-4E7D-8FA8-262FAA9C1195@isolar.DynDNS.ORG>
On Mon, 2015-11-09 at 23:18 -0800, Greg Earle wrote:
> > On Nov 9, 2015, at 9:48 PM, Ian Kent <raven@themaw.net> wrote:
> >
> > If there are directories that are possibly broken in some way then
> > to
> > clear them up the autofs managed mount point must be umounted.
> >
> > But if any mounts are busy at shutdown they are left mounted, and
> > the
> > autofs mount itself obviously must be left mounted too, then autofs
> > re
> > -connects to the mounts when it starts again.
>
> That's interesting, never knew that before. So maybe it thinks these
> phantom mounts should still be "mounted", and keeps trying to do it.
>
>
> > That complexity is the reason I usually just recommend a re-boot be
> > scheduled, plus if there is some sort of brokenness within the
> > mounted
> > autofs file system there's no knowing if there were side effects
> > when
> > it happened.
> >
> > Sorry, I'm not really much help with this.
>
> Well, I've already told Xymon to ignore these (at my peril!), so as
> long
> as they are just harmless messages, I'll live :-)
It's hard to know for sure if these indicate you're in for further
problems but there doesn't seem to be much you can do about it for the
time being.
As long as the system continues to provide the expected service then I
have to say it should be fine to ignore them.
But I always get a bit nervous when I see unexpected things like this
so I still recommend scheduling a re-boot. As long as you aren't seeing
other bad things happen the urgency of doing so isn't high.
So as and when the opportunity arises would be the thing to do. At
least get the request on the operations radar.
>
> Thanks for looking at the code just in case. Was hoping it might be
> something simple; obviously it wasn't.
>
> - Greg
>
> --
> To unsubscribe from this list: send the line "unsubscribe autofs" in
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
prev parent reply other threads:[~2015-11-10 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 21:03 "rmdir_path: lstat of <path> failed" issues, despite updated autofs RPM Greg Earle
2015-11-08 6:33 ` Ian Kent
2015-11-08 8:22 ` Greg Earle
2015-11-08 23:47 ` Ian Kent
2015-11-09 20:42 ` Greg Earle
2015-11-10 5:48 ` Ian Kent
2015-11-10 7:18 ` Greg Earle
2015-11-10 8:48 ` Ian Kent [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=1447145284.3028.8.camel@themaw.net \
--to=raven@themaw.net \
--cc=autofs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).