From owner-freebsd-stable@FreeBSD.ORG Sun Jan 20 14:47:28 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 82166D53 for ; Sun, 20 Jan 2013 14:47:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 42617714 for ; Sun, 20 Jan 2013 14:47:28 +0000 (UTC) Received: from ralph.baldwin.cx (c-68-39-198-164.hsd1.de.comcast.net [68.39.198.164]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 658DBB924; Sun, 20 Jan 2013 09:47:27 -0500 (EST) From: John Baldwin To: "Hub- Marketing" Subject: Re: 9-STABLE -> NFS -> NetAPP: Date: Sun, 20 Jan 2013 09:47:11 -0500 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.8.4; amd64; ; ) References: <201301190757.26398.jhb@freebsd.org> <7387292F-94CD-4643-91D4-748404B792F1@hub.org> In-Reply-To: <7387292F-94CD-4643-91D4-748404B792F1@hub.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Message-Id: <201301200947.11580.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Sun, 20 Jan 2013 09:47:27 -0500 (EST) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jan 2013 14:47:28 -0000 On Sunday, January 20, 2013 01:10:29 AM Hub- Marketing wrote: > On 2013-01-19, at 4:57 AM, John Baldwin wrote: > > On Tuesday, December 18, 2012 11:58:36 PM Hub- Marketing wrote: > >> I'm running a few servers sitting on top of a NetAPP file server =85 > >> everything runs great, but periodically I'm getting: > >>=20 > >> nfs_getpages: error 13 > >> vm_fault: pager read error, pid 11355 (https) > >=20 > > Are you using interruptible mounts ("intr" mount option)? >=20 > 192.168.1.253:/vol/vol1 /vm nfs rw,intr,soft,nolockd 0 = =20 > 0 >=20 > I just added the 'soft' option to the mix =85 nolockd is enabled since I = know > for a fact that its not possible for two processes to access the same file > on both mounts at the same time =85 Ah, ok. I just fixed a bug with interruptible mounts in HEAD where having a signal interrupt an NFS request returns EACCESS (13) rather than EINTR. You should retest with that fix applied. =2D-=20 John Baldwin