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

[Christian Niemeyer]

For me this is NOT FIXED. I did a clean install twice yesterday (October
16th) with the daily images of quantal (amd64).

1.) Clean install onto a flash drive. 2.) Clean install onto SATA HDD.
Both with the ext4 filesystem.

Both *never* shutdown cleanly. This really is problematic and makes the
filesystem inconsistent over time. At least there is a very high risk.
After a few re-boots I set tune2fs -c 1 /dev/sdX, to make sure that fsck
is forced to check every time, to avoid inconsistencies. And every
reboot or shutdown and boot fsck founds errors. The error messages "/ is
busy" are described here: https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1058987

I added some sync; sync; sync; and sleep 3 to /etc/init.d/unmountfs, and
some killall dnsmasq, etc. – it makes no differences. It hangs in the
end again on "/ device is busy", powers off, ==> unclean filesystem at
boot.

So far I lost one (testing) filesystem completely, which has become
totally inconsistent (on a new 400GB SATA HDD). My parallel
installations of 10.04 and 11.04 never had this behaviour.

If I unmount and boot the Live-CD/USB with these installer images and
doing an fsck on my fresh install filesystem on the hard drive, then
fsck also finds errors. Mostly something like "delated inodes has zero
dtime. FIXED."

PS: Also I tried to let the installer format my filesystem, and doing
the creating manually before the installer and just selecting it for
"/", not formatting. Makes no difference.

Hm, this really drives me crazy.

PS: I dropped precise because of this issue. Still remaining in quantal.
Good luck with fixing!

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