Ante, good eyes there. That statement is a little misleading, that "if
they're still running, they're supposed to be", as this assumes there
was an event somewhere between the running system, and runlevel [016],
which to my knowledge, there isn't.
I'm a little confused as to why umountfs is still running as part of rc,
and not in an upstart job. I'm pretty sure actually, that this is
related to bug #616287 , which I originally thought was mountall's
fault, but now it seems is in fact sysvinit's.
In any case, one solution could be to have umountfs emit 'unmounting-
filesystems' before it starts, and then change 'stop on runlevel [016]'
to 'stop on unmounting-filesystems'. If I understand initctl correctly,
it will wait for all of the triggered stops to complete before
continuing.
I also think that we should look at abstracting the events a bit more
for generic services so job writers don't have to become boot experts to
know when to start on / stop on.
Adding sysvinit task as well.
** Also affects: sysvinit (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in ubuntu.
https://bugs.launchpad.net/bugs/688541
Title:
race condition on shutdown (leads to corrupted fs)
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
