On Tue, Apr 29, 2014 at 8:17 AM, Donovan Watteau <[email protected]> wrote: > I have various mountpoints from a NetApp NFS server with I use on > OpenBSD/amd64 5.5. > > $ grep nfs /etc/fstab > server:/vol/foobar /vol/foobar nfs > noauto,rw,nodev,nosuid,noatime,noexec,nfsv3,tcp,soft,intr,noac,-x=300,-t=1000,acregmin=3,acregmax=5,-r=65536,-w=65536 > 0 0 > (and some other mountpoints with the same options)
That's a lot of knob turning. What documentation or testing led to you adding the tcp, noac, ac*, -x, -t, -r, and -w options? > However, when I do a simple "ls /vol/foobar" after an hour without > anything else using this mountpoint, this appears in the logs: > > Apr 29 13:53:46 puffy /bsd: receive error 54 from nfs server > server:/vol/foobar > Apr 29 13:53:48 puffy last message repeated 833 times > > $ grep 54 /usr/include/sys/errno.h > #define ECONNRESET 54 /* Connection reset by peer */ Is there an idle timeout on the server or flaky network (NAT?) between this client and the server? > ls(1) gets slowed down a bit, but works. The next ls(1) invocations > work fine, unless I stop using the mountpoint for about an hour. > This also happens when security(8) is called during the night > (when /vol/foobar isn't used for hours). > > Is it harmless or is there a real problem? Debian on the same machine > doesn't have this, but maybe OpenBSD is just a bit verbose about it? TCP connection is being dropped for some reason and then it takes a moment to be reopened when you try to use it again. Philip Guenther
