Using the nlink field is a practice that does not work for many file systems, at least VFAT/FAT32, NTFS, ISO9660, and likely the MacOS file systems as well. If you look at what contortions File::Find goes through to find out if the nlink value can be trusted, I guess it's better to either use File::Find, or to avoid the whole "optimization".