On Sat, 3 May 2014, Philip Guenther wrote: > On Fri, May 2, 2014 at 4:39 AM, Donovan Watteau <[email protected]> wrote: > * noac: a leftover, but removing it doesn't fix the problem. > > * ac: required for our use case. > > > How is that possible when you also set "noac" to *COMPLETELY DISABLE* > attribute caching? Is it not obvious that at least *one* of those settings > is completely bogus? This casts doubt on your claim that ac* are "required" > for your use case. > > ...
As I said, "noac" was a leftover (from an unrelated previous test). Which has no effect on the problem I was asking help for, because it still happens with "rw,noauto,tcp". > > Yes, I was wondering whether there is something left to be configured > > on the OpenBSD side to prevent that (since the problem doesn't show up > > on Debian running on the same machine), or should I look for a problem > > on the NFS server or Cisco side? > > > A TCP connection, which should be able to stay open, idle, indefinitely, is > being reset (as in, a packet with the RST flag is being received!). Linux > apparently decides to silently spend CPU and packets and hide that something > is breaking connections. If you're fine with that behavior, then just > ignore the error messages from the OpenBSD kernel: it retries the connection > for you already and is 'just' letting you know that your NFS server or > network hates you (and maybe you should fix that). If you don't like that > it does so, well, you have the source. So: there's indeed nothing to configure on OpenBSD to avoid this behaviour; the problem lies elsewhere in the network or with the NFS server (which I don't manage). That's what I wanted to know. I'm not bothering you any further. Thanks.
