From owner-freebsd-hackers Tue Dec 5 17:43:39 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA22097 for hackers-outgoing; Tue, 5 Dec 1995 17:43:39 -0800 Received: from news.csusb.edu (news.csusb.edu [139.182.2.13]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA22088 for ; Tue, 5 Dec 1995 17:43:29 -0800 Received: (from nwestfal@localhost) by news.csusb.edu (8.6.12/8.6.12) id RAA02672; Tue, 5 Dec 1995 17:42:43 -0800 Date: Tue, 5 Dec 1995 17:42:43 -0800 (PST) From: "Neal E. Westfall" To: hackers@freebsd.org Subject: free vnode isn't Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org Precedence: bulk I am running a news server on FreeBSD 2.1. This morning, while reading news on it with tin, we received an error message "free vnode isn't", at which point the kernel panic'd and the machine rebooted. At that point nobody could log in anymore, not even root from the console. The machine was running 951104-SNAP at the time. We have upgraded it to 2.1-RELEASE and seems to be running fine now. The news spindles are formatted to 2048 bytes per inode, and we did not run out of inodes at the time of the crash. Any help on what exactly happened, and how to recover from it withouth reinstalling the operating system would be greatly appreciated. Machine Configuration: 486DX4-100 AMD PCI motherboard Adaptec 2940 SCSI controller w/latest bios upgrade 1 540 MB Fujitsu, 4 1080 Fujitsu SCSI drives. SMC Etherpower PCI 32 MB ram Neal Westfall nwestfal@news.csusb.edu