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 mo=
unt?
> =
> If so, try taking out the "intr" option on the mount, if you are using it.
> =
> 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_getpa=
ges(),
> which is a pagein operation (and you don't want those to fail).
> =
> If you aren't using "intr", then I have no idea why a read would fail wit=
h EINTR.
I=92ve made the change on two of my servers that have been exhibiting NFS r=
elated issues, so we=92ll see how this goes over the next couple of days, b=
ut 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 server=
s using =91intr=92, this one server is the only one that I=92ve knowingly e=
xperienced the nfs_getpages, so it seems to be something hard to trigger =
=85
Thanks
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"