Messages in this thread | | | Date | Thu, 4 Sep 2003 00:37:22 -0400 | Subject | Re: [NFS] attempt to use V1 mount protocol on V3 server | From | Trond Myklebust <> |
| |
>>>>> " " == Pascal Schmidt <der.eremit@email.de> writes:
> Out of interest, how does this work? Not obvious to me since an > NFSv3 filehandle is too big for an NFSv2 server.
Most are not. An NFSv3 filehandle has a variable size (as opposed to NFSv2 which are fixed size), and so most NFS servers use the same filehandle for NFSv2 and NFSv3.
Note: The reason for this mess is that the early Linux-2.2.x knfsd servers were NFSv2 only. Unfortunately, the associated kmountd daemon would advertise that it did NFSv3 too, in which case it just returned the same NFSv2 filehandles. By retrying the GETATTR call in the NFSv3 client, and automatically switching to NFSv2 we were able to catch these buggy setups.
Note: The fact that we are now stuck with a schizophrenic NFSv3 client is one of the many reasons why I am now *very* wary of trying to work around server bugs by making fixes to the client code.
Cheers, Trond - 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/
| |