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

[watgrad]

I also am concerned about this hidden bug - I only discovered there was an issue when I noticed that boot times were longer than normal.  I have converted all my main computers to 12.10 64 bit...
They all show this behaviour with messaged like:
[    1.111309] EXT4-fs (sdb1): INFO: recovery required on readonly filesystem
[    1.111314] EXT4-fs (sdb1): write access will be enabled during recovery
...
[    2.127937] EXT4-fs (sdb1): orphan cleanup on readonly fs
[    2.127946] EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 30148324
[    2.128033] EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 30148284
[    2.128042] EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 30148298
[    2.128057] EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 44828301
[    2.128091] EXT4-fs (sdb1): 4 orphan inodes deleted
[    2.128093] EXT4-fs (sdb1): recovery complete

So I understand that this could lead to data loss? ...corrupt file
system?  I have tried to follow yota's suggested fix, but could not get
that to work.  On one laptop (macbookpro7,1 dual boot) shutting down
networking before shutting down the computer stops the behaviour - but
this is not true for the desktop systems (win7 dual boot).

The bug message says 'fix released' - how to I get and apply this fix?
(I already have the rec version of ifupdown...)

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