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

[Geoff Clare]

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.

* If the inode numbers are the same, the file might be the same file or it
might be a different file that has been assigned the same inode number.

The ambiguity in the second case can be avoided by obtaining the first inode
number from an open fd (which is then kept open) instead of a pathname.  (Or
an fd could be used to obtain the second inode number, as long as it was open
at the time the first inode number was obtained.)

(All of the above assumes that the device numbers are the same.)

    _______________________________________________________

Reply to this item at:

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

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