Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263676AbTEEQOe (ORCPT ); Mon, 5 May 2003 12:14:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263619AbTEEQOe (ORCPT ); Mon, 5 May 2003 12:14:34 -0400 Received: from smtp013.mail.yahoo.com ([216.136.173.57]:60941 "HELO smtp013.mail.yahoo.com") by vger.kernel.org with SMTP id S263676AbTEEQOc convert rfc822-to-8bit (ORCPT ); Mon, 5 May 2003 12:14:32 -0400 From: Michael Buesch To: Mike Waychison Subject: Re: processes stuck in D state Date: Mon, 5 May 2003 18:25:48 +0200 User-Agent: KMail/1.5.1 References: In-Reply-To: Cc: Zeev Fisher , linux kernel mailing list MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200305051826.01134.fsdeveloper@yahoo.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2130 Lines: 61 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 05 May 2003 17:24, Mike Waychison wrote: > On Mon, 5 May 2003, Michael Buesch wrote: > > On Monday 05 May 2003 07:52, Zeev Fisher wrote: > > > Hi! > > > > Hi Zeev! > > > > > I got a continuos problem of unkillable processes stuck in D state ( > > > uninterruptable sleep ) on my Linux servers. > > > It happens randomly every time on other server on another process ( all > > > the servers are configured the same with 2.4.18-10 kernel ). Here's an > > > example : > > > > [snip] > > > > > Has anyone noticed the same behavior ? Is this a well known problem ? > > > > I've had the same problem with some 2.4.21-preX twice (or maybe more > > times, don't remember) on one of my machines. > > IMHO it has something to do with NFS. (I'm using this box as a > > NFS-client). I wish, I could reproduce it one more time, to do some > > traces, etc on it. But I've not found a way to reproduce it, yet. > > This happens when you mount an NFS mount with the 'hard' option (default) > and a mount's handle expires incorrectly (eg: server crash). > Read the mount manpage for an explanation to the downsides of using > the 'soft' option. > > > Mike Waychison my fstab-entry: 192.168.0.50:/mnt/nfs_1 /mnt/nfs_1 nfs rw,hard,intr,user,nodev,nosuid,exec 0 0 from man mount: [snip] The process cannot be interrupted or killed unless you also specify intr. [/snip] I can't interrupt any process that accessed the NFS-server while shutting down the server, although intr is specified. _That's_ my problem. :) - -- Regards Michael B?sch http://www.8ung.at/tuxsoft 18:23:58 up 48 min, 3 users, load average: 1.20, 1.05, 0.93 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+tpCZoxoigfggmSgRAkmdAJwM/L8mZpS+DE2WzjzrXuRdxuY98QCgin1l aKik6/WGFwWXMjd8pjwHIXw= =akJd -----END PGP SIGNATURE----- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/