NFS client fails to disconnect - node become unresponsive about talos

[smira]

I won't recommend to use NFS today, as it was designed for a totally different usecase.

It's not expected though to have issues as long as NFS server is still responsive. Once NFS server becomes unresponsive, things go wrong way with NFS, which can be partially mitigated with NFS mount options.

I'm not quite sure what in this issue can be attributed to Talos Linux, or anything missing in Talos Linux itself, as NFS is implemented in the kernel, and there's not much there we can do on the OS side vs. the things you can configure yourself.

[Daxcor69]

When I asked about this in Discord, I got the following message "there's a problem with NFSv4 due to missing statsd if I remember correctly". Does this mean v4 is not supported in Talos?

So I just trying to sort it out. I know nfs is not ideal, I get that. Prior to migrating to Talos, nfsv4 worked without the current issue I am having. So is this an issue of nfsv3?

[smira]

NFSv4 user-space daemons are not enabled, but I believe it won't mount simply with v4.