[Bug 224047] Re: incorrect system shutdown when running git-daemon-run

Steve Langasek steve.langasek at canonical.com
Fri May 17 21:27:42 UTC 2013


There is always some possibility that the shutdown scripts will not be
able to remount the root filesystem read-only because rogue processes
refuse to die.  This is exceptional, and indicates a bug in those
scripts, *not* in sysvinit for failing to kill them (because believe me,
it tries).

Reassigning to git-core.

** Package changed: sysvinit (Ubuntu) => git-core (Ubuntu)

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

Title:
  incorrect system shutdown when running git-daemon-run

Status in “git-core” package in Ubuntu:
  Confirmed

Bug description:
  On hardy, if you install git-daemon-run a new service is created and handled incorrectly by "runsv" and not "upstart" as all other services (https://bugs.launchpad.net/ubuntu/+source/git-core/+bug/74135)
  On system shutdown we ask "runsv" and "runsvdir" to terminate, but they refuse (as seen in https://bugs.launchpad.net/ubuntu/+source/git-core/+bug/224041). 
  This refusal interacts in some weird manner with the synchronization of data on the main root partition so that on the next boot fsck needs to be run to fix errors left behind.

  I tested 4 times this scenario:
  * login to system
  * manually kill runsv and runsvdir by repeating:
    kill -9 `pidof runsv` `pidof runsvdir`
  * reboot
  * while booting the system notice no file system check is needed.

  And several times this one:
  * login
  * (don't do anything to disturb runsv, or runsvdir)
  * reboot
  * notice that file system checks are done and some errors appear to have been detected and fixed (fsck exits with error code 3). The system automatically reboots.
  * while booting the new system notice no file system check is needed again.

  It seems that because runsv's and runsvdir's refuse to terminate some
  data does not get flushed to disk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git-core/+bug/224047/+subscriptions




More information about the foundations-bugs mailing list