From owner-freebsd-current Tue Dec 9 20:35:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13305 for current-outgoing; Tue, 9 Dec 1997 20:35:03 -0800 (PST) (envelope-from owner-freebsd-current) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA13291 for ; Tue, 9 Dec 1997 20:34:54 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id WAA20572 for freebsd-current@freebsd.org; Tue, 9 Dec 1997 22:34:50 -0600 (CST) From: Kevin Day Message-Id: <199712100434.WAA20572@home.dragondata.com> Subject: 971208 and the nfs rollback didn't fix it... To: freebsd-current@freebsd.org Date: Tue, 9 Dec 1997 22:34:50 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I grabbed everything on 971208, hoping it would cure my nfs problems... It didn't. :) I still will see on my console: shell syslogd: sendto: no buffer space available Which is my first symptom that i'm going to have to reboot... Any attempt to read a file on an nfs system will completely hang the process. (kill -9 doesn't even get rid of it). 3028 mbufs in use: 2111 mbufs allocated to data 304 mbufs allocated to packet headers 11 mbufs allocated to protocol control blocks 2 mbufs allocated to socket names and addresses 554/1392 mbuf clusters in use 8694 Kbytes allocated to network (97% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines A reboot advises me that not all processes died, check ps axl, then it locks up. This system is a dual P/200, acting as an nfs client.... Both machines(this client, and a 2.2.1 server) get random 'nfsd send error 55's on them... Is this news to anyone? Kevin