I just had a look at 2.2.10's nfs client. We don't use the fsid value.
In principle to different files could have the same fileid and different
fsids, couldn't they?
> In order for the NFS client to guarantee they're the same file locally,
> the server needs to give both instances of the file the same handle.
> If it doesn't, the server has no clue what the client will do because
> of the "no conclusions can be drawn." I agree that the language is a
> bit confusing.
I don't think it matters. Locally the client may think they're two
different files, but updating one will show up in the
other... eventually.
> My problem is actually when the server does give the same file (i.e.,
> same fileid) two different handles because it wants the client to
> think they are different files. For example, the server exports the
> same volume twice.
I think the server can give two different handles even for the same
file. For example the user-space server used on Linux use a mysterious
hash-assist of the path name in the handle -- this presumably means
different handles for different paths, even when they're the same file.
This works ok because the fileid values are the same.
If this isn't good enough, let me know because I'm about to do the same
sort of thing in my own nfs server!
-- 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/