man nfs
man nfs
Posted Mar 6, 2020 19:45 UTC (Fri) by flussence (guest, #85566)In reply to: man nfs by willy
Parent article: Quote of the week
To be clear and just so I'm not constantly complaining: the other 99% of the time it works it's fantastic. I'm grateful for all the work that went into this. Even if these few sore spots don't get fixed, I feel less frustrated just having the acknowledgement that it's like that sometimes and I'm not imagining it.
Posted Mar 6, 2020 19:54 UTC (Fri)
by willy (subscriber, #9762)
[Link]
I didn't remove any places which would have been interruptible before, so the only difference is that now non-fatal signals won't interrupt a read.
Posted Mar 16, 2020 22:29 UTC (Mon)
by nix (subscriber, #2304)
[Link] (2 responses)
Posted Mar 19, 2020 8:33 UTC (Thu)
by flussence (guest, #85566)
[Link] (1 responses)
Posted Mar 19, 2020 22:09 UTC (Thu)
by nix (subscriber, #2304)
[Link]
man nfs
man nfs
I've had hung mounts that I'm pretty certain were caused by jumbo ethernet frames too - any mtu above about 4000 seems flaky.
It must be more than that: I've never had hung mounts on the link to the NFS server here, which has an MTU of 6128 (because of limits on one of the network cards in question), not on NFSv3 nor NFSv4.0 nor NFSv4.1. And if I had hung mounts, I'd know it: my $HOME is on NFS...
man nfs
man nfs
