From owner-freebsd-stable@freebsd.org Sat Aug 29 21:31:53 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9AE39BFD70 for ; Sat, 29 Aug 2015 21:31:53 +0000 (UTC) (envelope-from lists@searchy.net) Received: from j006.host001.searchy.nl (j006.host001.searchy.nl [79.143.214.199]) by mx1.freebsd.org (Postfix) with ESMTP id 8394FCFF for ; Sat, 29 Aug 2015 21:31:53 +0000 (UTC) (envelope-from lists@searchy.net) Received: from [192.168.5.21] (5418453B.cm-5-1b.dynamic.ziggo.nl [84.24.69.59]) (Authenticated sender: ppi@j006.host001.searchy.nl) by j006.host001.searchy.nl (Postfix) with ESMTPSA id BE63E1E8C07 for ; Sat, 29 Aug 2015 21:31:44 +0000 (UTC) Message-ID: <55E224BE.5000900@searchy.net> Date: Sat, 29 Aug 2015 23:31:42 +0200 From: "Frank de Bot (lists)" User-Agent: Mozilla/5.0 (X11; Linux i686; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: NFS Client changing it's source address? (FreeBSD 10.2) Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Aug 2015 21:31:53 -0000 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