From owner-freebsd-net Fri Sep 13 6:17:39 2002 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D622137B400; Fri, 13 Sep 2002 06:17:37 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3DCF43EAA; Fri, 13 Sep 2002 06:17:33 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA07230; Fri, 13 Sep 2002 09:17:33 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g8DDH3U73788; Fri, 13 Sep 2002 09:17:03 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15745.58702.945886.573972@grasshopper.cs.duke.edu> Date: Fri, 13 Sep 2002 09:17:02 -0400 (EDT) To: Gordon Tetlow Cc: net@FreeBSD.org, dillon@FreeBSD.org Subject: Re: ARP move hangs NFS mount In-Reply-To: <20020912181509.GY42734@roark.gnf.org> References: <20020912181509.GY42734@roark.gnf.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Gordon Tetlow writes: > I see this behavior on 4.6.1-RELEASE-p10: > > I have an EMC IP4700 NAS with 2 heads. On one head I have an active NFS share > that is being used by my FreeBSD webservers for content. When I reboot the > head that is actively hosting the NFS share, the other head arps up and takes > over the ip address of the head that just rebooted. My FreeBSD webservers see > the arp move but hang the NFS mount until the I reinstate the other head. As > a comparison, I tried this on a linux box and it continued along without a > hitch. Any ideas? I'll bet that when the second head takes over, it replies using its own IP address, rather the IP address of the head that it took over from. There's something about the FreeBSD NFS client implementation which requires that if you make an NFS request to a certain IP address, the reply MUST return from that same IP address. Otherwise, the reply will be ignored. Matt -- Do you know off the top of your head what makes this happen? While I realize that its a security feature, its caused me no end of suffering at two different sites, and I'd really like to know how to disable it! ;) Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message