lkml.org 
[lkml]   [1999]   [Jul]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: NFSv3 support (bugs, some fixes, and more)
Michael Kaminsky wrote:
> RFC 1813 (NFSv3) says
>
> To the client, the file handle is opaque. The client stores file
> handles for use in a later request and can compare two file
> handles from the same server for equality by doing a
> byte-by-byte comparison, but cannot otherwise interpret the
> contents of file handles. 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. Servers should try
> to maintain a one-to-one correspondence between file handles and
> files, but this is not required. Clients should use file handle
> comparisons only to improve performance, not for correct
> behavior.
>
> From my reading of the above, if an NFS server returns a different
> file handle for two files that are hard-linked (i.e., the same file
> on the server), the client cannot assume that they are the same ("no
> conclusions can be drawn"). So, in the hard link case, the server
> should be returning the same handle (and the same fileid), right?

My reading of it says: in the hard link case, the server MAY send the
same handle.

-- Jamie


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:52    [W:0.038 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site