Messages in this thread | | | Date | Tue, 13 Jul 1999 21:12:27 +0200 | From | Jamie Lokier <> | Subject | Re: NFSv3 support (bugs, some fixes, and more) |
| |
Michael Kaminsky wrote: > The server certainly is not required to send back the same filehandle > for hardlinked files, but it should. Otherwise, the client (linux > kernel) cannot assume the files are the same according to the RFC > (which in reality they are).
True the client can't assume the files are the same, but it can't assume they're different either.
> Currently, the kernel makes the assumption they are the same > implicitly, by only using fileid to lookup inodes.
This is not so bad because the RFC also says:
"fsid" is the file system identifier for the filesystem containing the file; "fileid" is a number that uniquely identifies the file within its filesystem
Note the "uniquely". But why do we not make use of the fsid value?
-- 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/
| |