Date: Sat, 29 Aug 2015 23:31:42 +0200 From: "Frank de Bot (lists)" <lists@searchy.net> To: freebsd-stable@freebsd.org Subject: NFS Client changing it's source address? (FreeBSD 10.2) Message-ID: <55E224BE.5000900@searchy.net>
next in thread | raw e-mail | index | archive | help
Hello, I have a server running FreeBSD 10.2. It has several NFS mounts. Frequently my NFS mount hang (v3). After a little investigation it looks like FreeBSD has chosen a wrong source address for it's connections and all packets are departing from the wrong interface. Sockstat output: [root@host004 ~]# sockstat -4 | grep 2049 root ssh 14689 3 tcp4 10.4.2.4:20499 10.4.2.5:22 ? ? ? ? tcp4 10.13.37.4:672 10.13.37.2:2049 ? ? ? ? tcp4 79.x.x.210:905 10.13.37.2:2049 ? ? ? ? tcp4 79.x.x.210:992 10.13.37.2:2049 tcpdump confirms nfs connection are trying to get out via the 79.x.x.x interface My fstab for the nfs mounts look like: 10.13.37.2:/tank/hostingbase /opt/jails/hostingbase nfs nfsv3,ro,noatime,async,noauto 0 0 /opt/jails/hostingbase /opt/jails/test01 nullfs ro,noatime,noauto 0 0 10.13.37.2:/tank/hosting/test /opt/jails/test01/opt nfs nfsv3,noatime,async,rw,noauto 0 0 tmpfs /opt/jails/test01/shm tmpfs rw,size=512000000,noauto 0 0 /opt/jails/hostingbase /opt/jails/test2 nullfs ro,noatime,noauto 0 0 10.13.37.2:/tank/hosting/test2 /opt/jails/test2/opt nfs nfsv3,noatime,async,rw,noauto 0 0 tmpfs /opt/jails/test2/shm tmpfs rw,size=512000000,noauto 0 0 The change of source address looks to be happening after a nfs connection is re-established. At first everything works, I leave the server idling (it's a test server) and after that the mounts are hanging 10.2-RELEASE #0 r286666 is the current running version. Regards, Frank de Bot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55E224BE.5000900>