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

[Paul Eggert]

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

>> if some Linux-based file systems can't provide stable
>> inode numbers, they should be fixed so that they do. It
>> shouldn't be that hard.
>
> It's not hard, it's impossible.  Take for example path
> based network filesystems (smbfs, sshfs).  For these the
> only identifier for files is the path.

If files are identified by the path, then you can hash the
path.  If you use a good 64-bit hash the chance of collision
is practically zero.  That's good enough.

I may sound a bit impatient here, but it's impatience for a
reason.  Knowledge of file serial numbers must be hardwired
into thousands of programs.  We can't change them all.  If you
have to support inodes by some inefficient means, then I'm
afraid that's what you'll have to do.  (Or, if you prefer,
you can warn users of these file systems that they will
break lots of programs.  :-)


    _______________________________________________________

Reply to this item at:

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

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