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

[Eric Blake]

Follow-up Comment #1, bug #17877 (project findutils):

> There are several Linux filesystems (including smbfs, fat, and
> some FUSE based ones) which cannot provide stable inode numbers
> for unreferenced files or directories.

That's the problem.  If an OS can't provide stable inode numbers, it is not
POSIX compliant.  find shouldn't have to bend over backwards to work around
broken file systems.  You should be reporting this bug to the file system
people.  cygwin manages to provide stable inode numbers for FAT just fine.

That said, it would be nice if fts could recognize such broken file systems
and work around their flaws.  But that is an issue for gnulib, not findutils,
since find 4.3.0 is the first version to use gnulib's fts instead of its own
homegrown traversal routines.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?17877>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/