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

[Christian Niemeyer]

Final release images tested. Clean standard install, default options on
400GB HDD. Still "/ device is busy".

Shutdown standard. Log out. And in lightdm > Reboot. Problem remains!
With the Live DVD testing the filesystem after shutdown and booting the
DVD instead, it says:

"sudo fsck.ext4 -Ffy /dev/sdb1
e2fsck 1.42.5 (29-Jul-2012)
quantalx64: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (4431956, counted=4432263).
Fix? yes

Free inodes count wrong (513823, counted=513874).
Fix? yes

quantalx64: ***** FILE SYSTEM WAS MODIFIED *****"


**PS**: Still remains that "sudo service dbus stop" and/or "sudo service networking stop" hangs for about 10 seconds. I think the problem remains, that dbus is not shut down cleanly.

-- 
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