Follow-up Comment #4, bug #23443 (project findutils):
All tests today done with find-4.4.0
Features enabled: D_TYPE O_NOFOLLOW(enabled) LEAF_OPTIMISATION FTS()
CBO(level=0)
-noloaf makes no difference.
Trying with different -maxdepth <n> settings makes a strange difference, as
it caused the issue to disappear, thus ending my tests.
Tests done as root, who is an unprivileged user with regard to these nfs
filesystems.
I found, that identical device/inode pairs exist under different
mountpoints.
find today complained about a filesystem loop.
stat showed that my ~/.snapshot/hourly.0 has the same dev/ino pair as its
parent, but different contents ... I admit, this is insane.
Should this cause sufficient confusion for find to skip directories that have
a different dev/ino pair?
Typescript attached.
(file #15776)
_______________________________________________________
Additional Item Attachment:
File name: typescript Size:8 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?23443>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
