Bug 235205
Summary: | lsof do not show files with link count less than 1 anymore | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Peter Bieringer <pb> |
Component: | lsof | Assignee: | Karel Zak <kzak> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.4 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-05-31 09:51:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Peter Bieringer
2007-04-04 14:40:42 UTC
on FC6, lsof-4.78-3: # lsof +L | grep libslang mc 20791 kzak mem REG 253,0 911464 1 1337214 /usr/lib64/libslang.so.2.0.7 # cp /usr/lib64/libslang.so.2.0.7 /usr/lib64/libslang.so.2.0.7.org # rm -f /usr/lib64/libslang.so.2.0.7 # lsof +L1 | grep libslang (nothing) # /usr/sbin/lsof +L | grep libslang mc 20791 kzak DEL REG 253,0 1337214 /usr/lib64/libslang.so.2.0.7 .. "+L" doesn't report zero as NLINK, there is empty space only. The lsof reports deleted files by the "DEL" in TYPE field. It means "lsof +L1" is probably not the best way how to check for deleted libraries. There is some info about it in lsof FAQ: 10.4.2 Why is neither link count nor size reported for some Linux ``DEL'' and ``mem'' file types? Link count and size are not reported for some entries from the process' ``maps'' file because a stat(2) of the entry file path failed or stat(2) delivered device or inode numbers that don't match the ones in the ``maps'' entry. When the stat(2) device or inode numbers don't match those in the ``maps'' file entry, it is likely that the stat(2) results don't apply to the file that was originally mapped by the process and whose path appears in the ``maps'' file entry, so lsof tries to avoid reporting possibly incorrect information. See the answer to the "What do ``path dev=xxx'' and ``path inode=yyy'' mean in the NAME column of Linux ``mem'' file types?" for more information on how mismatched stat(2) device and inode numbers are reported. I hope it helps. |