I completely agree, this patch is not the final solution - it's just a 'sticking plaster'. Better solutions must include changes to Upstart which ultimately must handle system shutdown internally. Maybe there's a case for adding a shutdown event which then blocks new services & tasks from starting (like shutdown does for logins) and enforces the kill timeout.
I would hate to see a system shutdown 'hanging' in a recovery shell simply because of a few open files. Umount must be made more resilient. Maybe we need a force option - try gently at first and if that fails then at certain critical conditions, like shutdown, the umount can be forced. The issue of open/deleted files can then be addressed after umount is complete. What worries me most is the damage to the journal that I saw during my first experience with this problem. I ran fsck in manual mode to repair the damage, which it eventually managed, but it left the ext3 disk without a journal. I had to manually fix this by running tune2fs -j. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/616287 Title: umountfs doesn't cleanly unmount / on reboot -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
