Date: Sun, 10 Feb 2013 19:31:06 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: Marc Fournier <scrappy@hub.org> Cc: freebsd-stable@freebsd.org, John Baldwin <jhb@freebsd.org> Subject: Re: 9-STABLE -> NFS -> NetAPP: Message-ID: <1946688889.2870936.1360542666536.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <461A7DB1-4693-4AA5-B43C-5F15FE0C4918@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Marc Fournier wrote:
> Hi John =E2=80=A6
>=20
> Does this help?
>=20
> root@io:~ # ps auxl | grep du
> root 1054 0.0 0.1 16176 6600 ?? D 3:15AM 0:05.38 du -skx /vm/2799 0
> 81426 0 20 0 newnfs
> root 12353 0.0 0.1 16176 5104 ?? D Sat03AM 0:05.41 du -skx /vm/2799 0
> 91597 0 20 0 newnfs
> root 64529 0.0 0.1 16176 5164 ?? D Fri03AM 0:05.40 du -skx /vm/2799 0
> 43227 0 20 0 newnfs
> root 12855 0.0 0.0 16308 1988 0 S+ 5:26AM 0:00.00 grep du 0 12847 0 20
> 0 piperd
It is probably too late, but all the lines (without the | grep du) would be
more useful. I also include the "H" flag, so it lists threads as well as
processes. The above just says the "du" command is waiting for a vnode lock=
.
The interesting process/thread is the one that is holding a vnode lock
while waiting for something else.
Are you still getting the:
nfs_getpages: error 13
vm_fault: pager read error, pid 11355 (https)
messages logged?
With John's recent patch, the error# would no longer be 13 if it was
caused by the "intr" flag resulting in a Read RPC terminating with EINTR.
If you are still getting the above with "error 13", it suggests that
the server is replying EACCES for the Read RPC.
I suggested before that you check to make sure that the executable had
read access for everyone one the file server. Since I didn't hear back,
I'll assume this is the case.
rick
ps: If it is still up and hasn't been rebooted, you could:
sysctl debug.kdb.break_to_debugger=3D1
- then type <ctrl><alt><esc> at the console and do the following
from the debugger
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ke=
rneldebug-deadlocks.html
How well this work depends on what options your kernel was built with.
> root@io:~ # grep vm /etc/fstab
> 192.168.1.254:/vol/basic /vm nfs rw,nolockd,intr 0 0
>=20
> Haven't rebooted yet =E2=80=A6 if there is anything I can do / try before=
=E2=80=A6 ?
>=20
> The kernel is from Jan 21st =E2=80=A6
>=20
>=20
> On 2013-01-19, at 4:57 AM, John Baldwin <jhb@freebsd.org> wrote:
>=20
> > 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 =E2=
=80=A6
> >> everything runs great, but periodically I'm getting:
> >>
> >> nfs_getpages: error 13
> >> vm_fault: pager read error, pid 11355 (https)
> >
> > Are you using interruptible mounts ("intr" mount option)?
> >
> > Also, can you get ps output that includes the 'l' flag to show what
> > the processes are stuck on?
> >
> > --
> > John Baldwin
>=20
> _______________________________________________
> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1946688889.2870936.1360542666536.JavaMail.root>