Hi, I've been working on NFS over the AF_VSOCK transport (https://www.spinics.net/lists/linux-nfs/msg60292.html). AF_VSOCK resets established network connections when the virtual machine is migrated to a new host. The NFS client expects file handles and other state to remain valid upon reconnecting. This is not the case after VM live migration since the new host does not have the NFS server state from the old host. Volatile file handles have been suggested as a way to reflect that state does not persist across reconnect, but the Linux NFS client does not support volatile file handles. I saw NFS 4.1 has a way for a new server running with the same network address of an old server to communicate that it is indeed a new server instance. If the server owner/scope in the EXCHANGE_ID response does not match the previous server's values then the server is a new instance. The implications of encountering a new server owner/scope upon reconnect aren't clear to me and I'm not sure to what extent the Linux implementation handles this case. Can anyone explain what happens if the NFS client finds a new server owner/scope after reconnecting? Thanks, Stefan
Attachment:
signature.asc
Description: PGP signature
