From: "Lever, Charles" Subject: RE: processes stuck in D state Date: Tue, 6 May 2003 08:47:28 -0700 Sender: nfs-admin@lists.sourceforge.net Message-ID: <482A3FA0050D21419C269D13989C611312747A@lavender-fe.eng.netapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Cc: , "linux kernel mailing list" , "Zeev Fisher" Return-path: Received: from mx01.netapp.com ([198.95.226.53]) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 19D4fO-0000V8-00 for ; Tue, 06 May 2003 08:47:42 -0700 To: "Michael Buesch" Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: > To reproduce the problem: > - - mount some nfs from a server in your lan. > - - Open an app, that uses the mounted fs. I've simply opened a > konqueror-window for the directory where the nfs is mounted. > - - shut down or crash the server or just pull the network-cable. > - - Now the konqueror-process is nonkillable in D state. There's no > chance to kill it. does the problem persist after you reconnect the network cable? what happens when the server becomes available again? are you mounting with UDP or TCP? ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs