Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 4 Dec 2001 04:23:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 4 Dec 2001 04:23:19 -0500 Received: from nick.dcs.qmul.ac.uk ([138.37.88.61]:42155 "EHLO nick.dcs.qmul.ac.uk") by vger.kernel.org with ESMTP id ; Tue, 4 Dec 2001 04:22:52 -0500 Date: Tue, 4 Dec 2001 09:22:51 +0000 (GMT) From: Matt Bernstein To: cc: Subject: Re: nfs: task can't get a request slot In-Reply-To: Message-ID: X-URL: http://www.theBachChoir.org.uk/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Have a look at adglinux1 and see if its NFS server is still alive. Your hung processes should "unhang" when rpppc1 can see the server again. On Dec 3 nbecker@fred.net wrote: [snip] >What does this mean? > >Dec 3 08:53:54 rpppc1 kernel: nfs: server adglinux1 not responding, still trying >Dec 3 08:53:54 rpppc1 kernel: nfs: server adglinux1 not responding, still trying >Dec 3 08:55:09 rpppc1 rpc.mountd: authenticated mount request from 139.85.108.152:890 for /disk1/nbecker (/disk1) >Dec 3 08:55:43 rpppc1 kernel: nfs: task 3408 can't get a request slot >Dec 3 08:55:43 rpppc1 kernel: nfs: task 3409 can't get a request slot [snip] - 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/