Date: Fri, 4 Jul 2014 09:33:48 -0700 From: Marc Fournier <scrappy@hub.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 10.x + LiquidSoap + NFS == Server Hang Message-ID: <AC3D8C79-76AD-4E55-A4D2-A8190FBB96A2@hub.org> In-Reply-To: <1805070922.7180203.1404475828988.JavaMail.root@uoguelph.ca> References: <1805070922.7180203.1404475828988.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 4, 2014, at 05:10 , Rick Macklem <rmacklem@uoguelph.ca> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AC3D8C79-76AD-4E55-A4D2-A8190FBB96A2>