From: Haakon Riiser Subject: Re: "Server not responding" after periods of client inactivity Date: Tue, 9 Aug 2005 22:32:19 +0200 Message-ID: <20050809203219.GA6740@fox.upc.no> References: <20050714212514.GA23867@fox> <20050730131031.GA1668@fox> <1122732943.8248.13.camel@lade.trondhjem.org> <20050730143216.GA2339@fox> <1122735345.8248.28.camel@lade.trondhjem.org> <20050809190634.GA5779@fox.upc.no> <1123614892.8245.166.camel@lade.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: nfs@lists.sourceforge.net Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] helo=mail.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30) id 1E2cTG-0006pL-1w for nfs@lists.sourceforge.net; Tue, 09 Aug 2005 15:21:18 -0700 Received: from externalmx-1.sourceforge.net ([12.152.184.25]) by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44) id 1E2buI-0007e6-QC for nfs@lists.sourceforge.net; Tue, 09 Aug 2005 14:45:11 -0700 Received: from pat.uio.no ([129.240.130.16] ident=7411) by externalmx-1.sourceforge.net with esmtp (TLSv1:AES256-SHA:256) (Exim 4.41) id 1E2aos-00014F-OF for nfs@lists.sourceforge.net; Tue, 09 Aug 2005 13:35:31 -0700 Received: from mail-mx4.uio.no ([129.240.10.45]) by pat.uio.no with esmtp (Exim 4.43) id 1E2am4-0004U4-9Z for nfs@lists.sourceforge.net; Tue, 09 Aug 2005 22:32:36 +0200 Received: from cm-80.111.122.093.chello.no ([80.111.122.93] helo=fox.venod.com) by mail-mx4.uio.no with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id 1E2alu-0002I7-T4 for nfs@lists.sourceforge.net; Tue, 09 Aug 2005 22:32:26 +0200 To: Trond Myklebust In-Reply-To: <1123614892.8245.166.camel@lade.trondhjem.org> Sender: nfs-admin@lists.sourceforge.net Errors-To: nfs-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Post: List-Help: List-Subscribe: , List-Archive: 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