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.
I confirm this problem in ubuntu 14.04: upstart/ mysql.log. 1 (deleted)
$ sudo lsof|grep deleted|grep -Ev "/(dev|tmp|run)"
init 1 root 10w REG 252,4 778 131190 /var/log/
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.