Comment # 4 on bug 976863 from Michael Andres

> [See e.g. http://ftp.tuwien.ac.at/utils/admin-tools/lsof/FAQ : 
> 10.4.1  What do ``path dev=xxx'' and ``path inode=yyy'' mean in the NAME column of Linux ``mem'' file types?]
> 
>       When the device or inode number in the process' ``maps'' file
>       entry doesn't match the stat(2) results from the file path,
>       lsof reports the inconsistent information from the stat(2) of
>       the path parenthetically after the path in the NAME column
>       in one of these forms.
>       ...
>       Device and inode inconsistencies can occur when a file at a
>       ``maps'' path is replaced after the process has started, or
>       when a different file system with similar path names is mounted
>       on top of the original file system.

The files appear to be deleted because lsof suppresses the reporting of link
count due to a detected device mismatch. Indicated by the appended '(path
dev=0,33)'. In fact we can't tell for sure what the state of those files is.

Maybe the vanilla kernel treats the root partition mount different than the
kernel-default. I'm forwarding this to the kernel-maintainers, maybe they can
explain why, and/or how to fix it.