On Fri, Apr 27, 2012 at 12:05:44PM -0400, Chuck Lever wrote: > 2. The current Linux NFS server implementation does not tolerate UCS clients > > I tried a simple test with the Linux UCS client and current stock NFS server implementations. I mounted each server via NFSv4.0 by its IPv4 and its IPv6 address. The UCS client's server trunking discovery algorithm should recognize that these addresses represent the same server instance. For a Solaris 11 FCS server, this worked as expected. > > For the Linux Fedora 16 server, this test failed. The server returned a different clientid4 for the second mount, even though the client presented the same nfs_client_id4 and boot verifier, and the first mount's lease had not expired. In addition, the server responded with NFS4ERR_CLID_INUSE when the client attempted a SETCLIENTID_CONFIRM. The second mount was thus prevented. The Linux NFS community agrees the Linux server's behavior is incorrect. Yep. Note though that both failures are probably due to the rpc's arriving from two different client addresses, rather than to two different server addresses. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
