On 06/26/2016 03:59 AM, Ian Kent wrote:
The autofs4_d_automount() entry here indicates this is the one that triggered the mount. If you are seeing a problem with mount, looking for the blocked process and killing it should clear the rest of these up. You would think that, even if mount.nfs(8) was losing network packets, it would timeout after about 3 minutes. I must admit I haven't waited long enough to find out if that's the case so far. If you find you are actually seeing this, setting the configuration option mount_wait to some sensible value sufficient for a mount to complete might help.
Thanks for the quick response. I don't remember seeing any lingering mount.nfs, but I must have overlooked.
However, I've also had those "deadlocks" happen with several different NFS servers at the same time (this was not the case with the traces I sent in my previous email). If one NFS server was unmountable, should automount be blocked when trying to mount others?
Anyway, I'll investigate some more next time the "deadlock" occurs and will also try setting mount_wait to a reasonable value. I'll let you know how it goes.
-- Cyril B. -- To unsubscribe from this list: send the line "unsubscribe autofs" in
