[Bug 578536] [NEW] when stopped, automount orphans some mounts

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Chris J Arges (christopherarges):

Binary package hint: autofs5

I have an automount setup containing a large number of NIS-provided
maps, all derived from an NIS-provided master map (yp:auto.master). When
I stop automount using "stop autofs", I noticed that some mounts have
been unmounted while a non-deterministic number of mounts have been
orphaned and need to be cleaned up using "umount":

adar at adar-lx:~$ sudo start autofs && sudo stop autofs && grep autofs /proc/mounts
autofs start/running, process 13152
autofs stop/waiting
auto.home /exit14 autofs rw,relatime,fd=19,pgrp=13152,timeout=60,minproto=5,maxproto=5,indirect 0 0
/etc/auto.build /build autofs rw,relatime,fd=6,pgrp=13152,timeout=300,minproto=5,maxproto=5,indirect 0 0
auto.exit15 /exit15 autofs rw,relatime,fd=31,pgrp=13152,timeout=60,minproto=5,maxproto=5,indirect 0 0
auto.scripts /scripts autofs rw,relatime,fd=73,pgrp=13152,timeout=60,minproto=5,maxproto=5,indirect 0 0

adar at adar-lx:~$ sudo start autofs && sudo stop autofs && grep autofs /proc/mounts
autofs start/running, process 13198
autofs stop/waiting
/etc/auto.build /build autofs rw,relatime,fd=6,pgrp=13198,timeout=300,minproto=5,maxproto=5,indirect 0 0
auto.scripts /scripts autofs rw,relatime,fd=73,pgrp=13198,timeout=60,minproto=5,maxproto=5,indirect 0 0
auto.mts-tlv /mts-tlv autofs rw,relatime,fd=67,pgrp=13198,timeout=60,minproto=5,maxproto=5,indirect 0 0
auto.mts-sof /mts-sof autofs rw,relatime,fd=79,pgrp=13198,timeout=60,minproto=5,maxproto=5,indirect 0 0
auto.mts-cm /mts-cm autofs rw,relatime,fd=85,pgrp=13198,timeout=60,minproto=5,maxproto=5,indirect 0 0

adar at adar-lx:~$ sudo start autofs && sudo stop autofs && grep autofs /proc/mounts
autofs start/running, process 13244
autofs stop/waiting
auto.mts-sof /mts-sof autofs rw,relatime,fd=79,pgrp=13244,timeout=60,minproto=5,maxproto=5,indirect 0 0
auto.buildmap /bldmnt autofs rw,relatime,fd=49,pgrp=13244,timeout=60,minproto=5,maxproto=5,indirect 0 0
auto.exit26home /exit26 autofs rw,relatime,fd=55,pgrp=13244,timeout=60,minproto=5,maxproto=5,indirect 0 0

I suspect this is due to the transition to upstart but I'm not 100%
sure.

## SRU JUSTIFICATION ##
IMPACT: Running reload autofs on a release with this issue creates automount maps and can cause the automounter to hang. This will prevent logins via ssh for users (due to NFS mounted home directories).

FIX: Patch cherry picked from upstream,
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/578536/comments/6

PATCH: see diff in unapproved queue.

REPRODUCE: See this bug description

DISCUSSION: Issue was known and resolved upstream, and has been carried
in later releases of Ubuntu.  The patch coming untouched from upstream
indicates that the regression potential is low.

** Affects: autofs5 (Ubuntu)
     Importance: Medium
     Assignee: Ubuntu Server Team (ubuntu-server)
         Status: Fix Released

** Affects: autofs5 (Ubuntu Lucid)
     Importance: Medium
     Assignee: Dave Walker (davewalker)
         Status: Fix Committed

** Affects: autofs5 (Ubuntu Maverick)
     Importance: Medium
     Assignee: Dave Walker (davewalker)
         Status: Fix Committed

** Affects: autofs5 (Ubuntu Natty)
     Importance: Medium
     Assignee: Chris J Arges (christopherarges)
         Status: Confirmed

** Affects: autofs5 (Ubuntu Oneiric)
     Importance: Medium
     Assignee: Ubuntu Server Team (ubuntu-server)
         Status: Fix Released


** Tags: server-o-rs verification-needed
-- 
when stopped, automount orphans some mounts
https://bugs.launchpad.net/bugs/578536
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.