I confirm this problem in ubuntu 14.04: $ sudo lsof|grep deleted|grep -Ev "/(dev|tmp|run)" init 1 root 10w REG 252,4 778 131190 /var/log/upstart/mysql.log.1 (deleted)
An effect (and how I noticed it) is that when I take LVM snapshot of the underlying volume I get warning messages in dmesg: $ dmesg -T ... [Fri Mar 6 06:02:19 2015] bio: create slab <bio-1> at 1 [Fri Mar 6 06:02:19 2015] EXT4-fs (dm-6): 1 orphan inode deleted [Fri Mar 6 06:02:19 2015] EXT4-fs (dm-6): recovery complete ... So the orphan inode in the snapshot (i.e. dm-6) gets deleted but it remains in the underlying volume. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1130611 Title: Upstart never closes /var/log/upstart/mysql.log Status in upstart package in Ubuntu: New Bug description: I ran "init u" after noticing a lingering FD to a log file that lsof showed as "(deleted)". However because the file handle is never closed, and the log files get logrotate'd it keeps happening, like so: init 1 root 11w REG 252,0 3532 394558 /var/log/upstart/mysql.log.1 (deleted) It's possible this might be fixed by a version update, as I noticed there were closed bugs relating to "leaked" file descriptors? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1130611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp