Messages in this thread | | | Date | Thu, 28 Dec 2006 19:17:36 +0100 (CET) | From | Mikulas Patocka <> | Subject | Re: Finding hardlinks |
| |
>> This sounds like a bug to me. It seems like we should have a one to one >> correspondence of filehandle -> inode. In what situations would this not be the >> case? > > Well, the NFS protocol allows that [see rfc1813, p. 21: "If two file handles from > the same server are equal, they must refer to the same file, but if they are not > equal, no conclusions can be drawn."] > > As an example, some file systems encode hint information into the filehandle > and the hints may change over time, another example is encoding parent > information into the filehandle and then handles representing hard links > to the same file from different directories will differ.
BTW. how does (or how should?) NFS client deal with cache coherency if filehandles for the same file differ?
Mikulas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |