On Mon, 2015-11-09 at 23:18 -0800, Greg Earle wrote: > > On Nov 9, 2015, at 9:48 PM, Ian Kent <raven@xxxxxxxxxx> 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
