I don't think this analysis is correct. At the time the umountfs script
finishes, *all* filesystems are supposed to be unmounted. This includes
any mount points watched by autofs. So why is autofs still running at
this point in the shutdown? The autofs daemon should be shut down
*prior* to /etc/rc6.d/S35networking, since at that point there's no
network left and autofs should no longer be trying to mount new
filesystems anyway!
And if I look at the autofs5 package, it has a wrong upstart job that
does 'stop on runlevel [!2345]', which does not properly serialize the
shutdown to ensure the service is stopped before we reach the unmounting
phase. Thus there's a race between /etc/init/rc.conf and
/etc/init/autofs.conf.
Reassigning to the autofs5 package.
** Package changed: sysvinit (Ubuntu) => autofs5 (Ubuntu)
** Changed in: autofs5 (Ubuntu)
Importance: Undecided => High
** Changed in: autofs5 (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) => Canonical
Server Team (canonical-server)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
https://bugs.launchpad.net/bugs/988394
Title:
Reboot hangs because /etc/rc6.d/S40umountfs chokes on non-existent
mounts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/988394/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
