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

dino99 1061639 at bugs.launchpad.net
Tue Oct 9 05:32:59 UTC 2012


On last shutdown in verbose mode, i've seen one more issue:

During the last part of the shutdown process, a comment is written and says: 
- trying to retrieve the remaining processes
- then, strangely, modemmanager is restarted and load its dozen drivers (got a modemmanager daily update "0.6.0.0.really-0ubuntu1). I've already seen randomly that drivers reload on shutdown in the past.
- and get : mount / is busy

With the next reboot, the booted partition has broken inodes:

oem at dub:~$ dmesg | grep orphan
[    8.812542] EXT4-fs (sdb5): orphan cleanup on readonly fs
[    8.819511] EXT4-fs (sdb5): ext4_orphan_cleanup: deleting unreferenced inode 400809
[    8.819581] EXT4-fs (sdb5): 1 orphan inode deleted

-- 
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:
  Triaged
Status in “ifupdown” source package in Quantal:
  Triaged

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




More information about the foundations-bugs mailing list