From owner-freebsd-questions Fri Feb 21 8:17:10 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2592437B401 for ; Fri, 21 Feb 2003 08:17:09 -0800 (PST) Received: from mx1.clickcom.com (mx2.clickcom.com [209.198.22.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7530643FAF for ; Fri, 21 Feb 2003 08:17:08 -0800 (PST) (envelope-from jsmailing@clickcom.com) Received: from aesop (calefaction.clickcom.com [209.198.22.19]) by mx1.clickcom.com (email) with ESMTP id E0DAA5EDA8; Fri, 21 Feb 2003 11:17:07 -0500 (EST) From: "John Straiton" To: Subject: New drive causing panics ffs_vfree Date: Fri, 21 Feb 2003 11:12:53 -0500 Message-ID: <003101c2d9c4$199ea540$1916c60a@win2k.clickcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I had a perfectly good, running 4.7 machine at home that serviced my dhcp, nat & samba needs. I ordered a new Western Digital 160GB drive for it and it came in last night. I decided this would be a great time to make a fresh start on the 5.X tree so I removed the other two drives from the machine and did an install from CD. The install went fairly smooth and in a few minutes I had a functional machine with 512M swap, 1G / , 1.5G /var, 5G /usr, 6G /home and a 135G /vol1 slice. After getting everything running, I started copying files to the /vol1 slice via SMB when I saw a kernel panic after about 30 seconds. Panic: ffs_vfree : freeing free inode dev = ad0s1g, ino=4, fs=/vol1 Upon rebooting, it'll give me a login prompt & start the background fsck. I'll log in quickly and then maybe after about 2 minutes the cursor will stop blinking and turn to a solid square. At that time I can no longer type to display on the screen. Sshd stops responding as well. Now here's the weird part. I can switch ttys just fine. I can also still access the internet from LAN'ed machines through my ipfilter/ipnat setup on this machine. I just can't use anything that I guess requires disk access. I went to bed to make sure that it wasn't just doing something that was just using 100% of the resources but upon getting up, it's still locked. I then rebooted and did a boot -s. Did a manual fsck which of course found errors, then 'exit'd to the login again. The machine locked up a few minutes later just as before so I don't believe it has anything to do with the background fsck. To further test, I booted to single user again, and then let it sit after it was done with an fsck. It locked just sitting there in single user mode. I can't imagine this drive is simply "too big". Help? John Straiton jks@clickcom.com Clickcom, Inc 704-365-9970x101 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message