Re: "Server not responding" after periods of client inactivity

[Haakon Riiser <haakon.riiser@fys.uio.no>]

Trond,

> Just means that the mountd process is stuck in a syscall. Have you tried
> getting a thread dump when it happens?
> echo "t" > /proc/sysrq-trigger
> on the server then scour through the 'dmesg' output until you find out
> where mountd is hiding.

Done.  Unfortunately, I couldn't find a call trace for mountd,
I only got this:

rpc.mountd    R running  1880  2814      1               18906 (NOTLB)

When mountd isn't hanging, I do get a call trace.  Also, I
noticed that  echo "t" > /proc/sysrq-trigger  didn't return
immediately while mountd was hanging.  Normally, it returns
almost instantaneously, but during the hang, it took a second or
two.  (Returned long before the hang was over, though.)

Btw, I saved the entire dmesg output, just in case.  Let me know if
you're interested, OK?

-- 
 Haakon


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs