From owner-freebsd-stable@FreeBSD.ORG Fri Jul 4 16:33:53 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 597A5F00 for ; Fri, 4 Jul 2014 16:33:53 +0000 (UTC) Received: from hub.org (hub.org [200.46.208.146]) by mx1.freebsd.org (Postfix) with ESMTP id 28EE92B12 for ; Fri, 4 Jul 2014 16:33:53 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.188]) by hub.org (Postfix) with ESMTP id 07899ED82F6; Fri, 4 Jul 2014 13:33:52 -0300 (ADT) Received: from hub.org ([200.46.208.146]) by maia.hub.org (mx1.hub.org [200.46.151.188]) (amavisd-maia, port 10024) with ESMTP id 55733-07; Fri, 4 Jul 2014 16:33:51 +0000 (UTC) Received: from [10.5.250.137] (remote.ilcs.sd63.bc.ca [142.31.148.2]) by hub.org (Postfix) with ESMTPA id 1F22AED82F5; Fri, 4 Jul 2014 13:33:50 -0300 (ADT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: FreeBSD 10.x + LiquidSoap + NFS == Server Hang From: Marc Fournier In-Reply-To: <1805070922.7180203.1404475828988.JavaMail.root@uoguelph.ca> Date: Fri, 4 Jul 2014 09:33:48 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1805070922.7180203.1404475828988.JavaMail.root@uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.1878.2) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2014 16:33:53 -0000 On Jul 4, 2014, at 05:10 , Rick Macklem wrote: > 4 is EINTR. That would suggest you might have the "intr" option on the = mount? >=20 > If so, try taking out the "intr" option on the mount, if you are using = it. >=20 > The problem with it is that, if anything posts a signal to a process = while > I/O is in progress it will fail. In this case the failure is in = nfs_getpages(), > which is a pagein operation (and you don't want those to fail). >=20 > If you aren't using "intr", then I have no idea why a read would fail = with EINTR. I=92ve made the change on two of my servers that have been exhibiting = NFS related issues, so we=92ll see how this goes over the next couple of = days, but am curious as to when one would use =91intr=92 in the first = place, if by using it, it could cause NFS to hang like this? Granted, = out of 11 servers using =91intr=92, this one server is the only one that = I=92ve knowingly experienced the nfs_getpages, so it seems to be = something hard to trigger =85 Thanks