find: WARNING: Hard link count is wrong....

andrew.46 · 11-13-2015, 05:06 PM

I have just moved to -current and all is well but I have noted an error with find:

Code:

root@ilium/home/andrew# find / -iname abcde
find: WARNING: Hard link count is wrong for `/proc/fs' (saw only st_nlink=6 but we already saw 4 subdirectories): this may be a bug in your file system driver.  Automatically turning on find's -noleaf option.  Earlier results may have failed to include directories that should have been searched.
/usr/bin/abcde
/home/andrew/mail/mailboxes/abcde
/home/andrew/.local/share/Trash/expunged/2895694272/usr/local/bin/abcde
/home/andrew/source/perl/abcde
/home/andrew/source/abcde
find: `/home/andrew/.gvfs': Permission denied
/home/andrew/development/abcde
/home/andrew/development/abcde/abcde
root@ilium/home/andrew#

Google does not have much to offer although this claims it can be ignored. Any thoughts?

Edit: Contents of proc fs:

Code:

andrew@ilium~$ ls -l /proc/fs
total 0
dr-xr-xr-x 3 root root 0 Nov 14 10:11 ext4
dr-xr-xr-x 3 root root 0 Nov 14 10:11 jbd2
dr-xr-xr-x 2 root root 0 Nov 14 10:11 lockd
dr-xr-xr-x 2 root root 0 Nov 14 10:11 nfsd
dr-xr-xr-x 2 root root 0 Nov 14 10:11 nfsfs
andrew@ilium~$

allend · 11-13-2015, 07:29 PM

This is an issue that I have seen using find on CIFS mounted filesystems from Windows machines. As is stated in the error message and the link you gave, just use the '-noleaf' option to find and live with the performance hit that arises from the additional stat calls.
It is an issue that arises when the mounted filesystem does not provide (from here)

Quote:

a value of at least 2 for the NumberOfLinks value on a directory like we expect with POSIX-y servers

andrew.46 · 11-13-2015, 08:16 PM

Thanks for your answer allend. To tell the truth the searches I normally undertake with find are usually a little more finely focused so rarely traverse /proc/fs. Still it is a little niggle...