I suspect I've just hit this issue while working within a chroot. After a suspend/resume cycle the external device hosting the file- systems mounted in the chroot are generating kernel read errors.
One file-system could not be umount-ed because a file was in use: $ sudo ls -l /proc/1/fd/ | grep target l-wx------ 1 root root 64 Feb 10 14:42 13 -> /target/var/log/upstart/ureadahead-other.log The job was stopped but the file remained open: $ initctl status ureadahead-other ureadahead-other start/killed, process 803 $ ps -efly | grep 803 S tj 1058 2828 0 80 0 940 2361 pipe_w 15:59 pts/4 00:00:00 grep --color=auto 803 $ sudo initctl start ## hangs indefinitely and needs Ctrl+C to exit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130611 Title: Upstart never closes /var/log/upstart/mysql.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1130611/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
