From owner-freebsd-current Tue Jan 1 11:25:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by hub.freebsd.org (Postfix) with ESMTP id 6AF0537B416 for ; Tue, 1 Jan 2002 11:25:52 -0800 (PST) Received: from laptop.6bone.nl (penguin.ripe.net [193.0.1.232]) by birch.ripe.net (8.11.6/8.11.6) with SMTP id g01JPol25689 for ; Tue, 1 Jan 2002 20:25:50 +0100 Received: (nullmailer pid 670 invoked by uid 1000); Tue, 01 Jan 2002 19:25:50 -0000 Date: Tue, 1 Jan 2002 20:25:50 +0100 From: Mark Santcroos To: current@freebsd.org Subject: fsck panic; ffs_vfree: freeing free inode Message-ID: <20020101202550.A317@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Handles: MS6-6BONE, MS18417-RIPE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG After a reboot due to a crash, fsck panic'ed on me with the following message: dev = ad0s1a, ino = 270, fs = / panic: ffs_vfree: freeing free inode This was with a kernel of Dec 20. To be sure I compiled a new kernel and world with recent sources but I still get the same panic with fsck. The system is on a IDE disk and softupdates are enabled, I don't seem to experience any data loss (if I skip the fsck at boot time). Any ideas or suggestions on how to fix this are very welcome. Multiple crashdumps are available. Thanks Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message