[Bug 1061639] Re: Upstartification of /etc/init.d/networking has lost deconfiguring-networking event causing bad side-effects

[yota]

To detect what is keeping / filesystem busy I put a:

lsof / > /openfiles.txt
sync

on top of /etc/init.d/umountroot

In my case it results that dhclient and dnsmasq are most likely to be the root cause; who is supposed to bring them down?
I disabled dnsmasq commenting dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf and add a "killall dhclient" in if-down.d and now shutdowns are clean on my 3 machines.

On the other hand "service networking stop" still takes ages to complete
(but only the first time you do it) which leads to think that there is
also something else which is not working properly with dbus.

This issue seems really critical to me as well: shutdown time is worsened (at least 3x in my case) while boot time suffers from time needed for fsck (which is triggered every time since the fs is dirty).
So both user experience is impaired and data integrity is at risk, but is not so clear against wich package to file a bug.
Expecially since it can be some weird interaction between them and I would not take for granted that ifupdown is not relevant anymore.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1061639

Title:
  Upstartification of /etc/init.d/networking has lost deconfiguring-
  networking event causing bad side-effects

Status in “ifupdown” package in Ubuntu:
  Fix Released
Status in “ifupdown” source package in Quantal:
  Fix Released

Bug description:
  In precise, /etc/init.d/networking was a true SysV service script that
  did the following:

  initctl emit deconfiguring-networking

  In quantal, /etc/init.d/networking is now using the upstart-job
  symlink back to the upstart job /etc/init/networking.conf.

  The problem is that the 'deconfiguring-networking' is no longer being
  emitted. This causes dbus to fail to stop on system shutdown which
  causes a cascading effect whereby other Upstart jobs are also not shut
  down. Eventually, the system halt with the message:

  mount: / is busy

  This results in a unclean shutdown which can result in FSCK being run
  / slow / bad user boot experience.

  The two main options here are:

  1) Re-instate the 'deconfiguring-networking' event.
  2) Change the dbus 'stop on' condition and update upstart-events.7 to remove 'deconfiguring-networking'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1061639/+subscriptions