Date: Thu, 3 Feb 2005 16:11:05 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Mohan Srinivasan <mohan_srinivasan@yahoo.com> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: Processes stuck in nfsreq Message-ID: <20050204001105.GA3760@xor.obsecurity.org> In-Reply-To: <20050203182917.40592.qmail@web80603.mail.yahoo.com> References: <20050203180756.GA2103@xor.obsecurity.org> <20050203182917.40592.qmail@web80603.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, Feb 03, 2005 at 10:29:16AM -0800, Mohan Srinivasan wrote: > Hi, > > In the info you have below, the NFS request was not sent (R_SENT > is not set). We didn't send out the request because possibly nm_cwnd > didn't allow us to send the request. If nfs_request() could not send > the request, then typically, the request would be retransmitted from > nfs_timer(). > > If nm_cwnd is full, then there must be a lot of outstanding requests > that haven't been replied to yet (on this mount), which is the fundamental > issue. FYI, this is truly hung and not just backlogged - it hasn't proceeded any further since last night. > Can you force a core dump and send me a pointer to it ? Unfortunately not, because twed dumping is still broken. The only way I was able to obtain this information is because kan has patches that fix kgdb enough to use it on the running kernel. > Also, after you force a core, can you also try a quick workaround - someone > else also reported NFS client hangs and said that things were fine > after they set mpsafenet to 0. It would be good to see if there's a > correlation there. I can try that. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCAr2ZWry0BWjoQKURAqV3AJ4wOuupBoGVf75mVJeSMDHb1tqHCACg7Tlq xxU355GFq1yiU7zH/SI3HZM= =Yazc -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050204001105.GA3760>