Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

Eric Blake <[EMAIL PROTECTED]> wrote: ... >> > > For the gnulib crowd, a summary of the above link is that find 4.3.0, > which uses gnulib's fts, is sometimes reporting "No such file or > directory" in the middle of traversal on non-POSIX file systems such as

Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [Replying outside of savannah, and adding bug-gnulib, since ultimately, the behavior in question is a result of gnulib's fts] According to Geoff Clare on 9/30/2006 5:53 AM: > Follow-up Comment #6, bug #17877 (project findutils): > > Good point about

[bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

Follow-up Comment #6, bug #17877 (project findutils): Good point about inode numbers being reused. This means that what you can tell from comparing inode numbers (obtained from pathnames), according to POSIX, is: * If the inode numbers are different, the file is definitely a different file. *