From owner-freebsd-questions@FreeBSD.ORG Wed Jun 1 15:21:40 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 BD17816A41C for ; Wed, 1 Jun 2005 15:21:40 +0000 (GMT) (envelope-from ean@hedron.org) Received: from prosporo.hedron.org (hedron.org [66.11.182.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 665C443D1F for ; Wed, 1 Jun 2005 15:21:40 +0000 (GMT) (envelope-from ean@hedron.org) Received: from hedron.org (unknown [192.168.89.1]) by prosporo.hedron.org (Postfix) with ESMTP id 724A3C12E for ; Wed, 1 Jun 2005 11:21:39 -0400 (EDT) Date: Wed, 1 Jun 2005 11:21:00 -0400 Mime-Version: 1.0 (Apple Message framework v553) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Ean Kingston To: freebsd-questions@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.553) Subject: kernel panic with unmount: dangling vnode on boot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 15:21:40 -0000 Hi all, I just updated my 5.3 system to 5.4p1 from source and ran into a serious problem. During boot, when the filesystems are being mounted, the system goes into a kernel panic and reports "panic unmount: dangling vnode" it then reboots. I have found PR 79665 which appears to be related. I have also found that booting to single user mode and manually mounting the filesystems will bypass this problem but it is not a good workaround since I don't have battery backup and the power here is less than ideal (short outages 3 or 4 times a year). The system this is being tested on is using gvinum for a number of filesystems: /tmp is stripped, /home is mirrored, / /var /usr are ordinary filesystems. The system is a dual PIII so I'm using an SMP kernel. I've stripped unused device drivers and added a few things so I will re-try with generic and generic+smp when I get a chance. Once I get the system back up (after the most recent reboot) I will build a generic kernel and see if that has the same problem. Does anyone else have similar problems and, if so, are there any workarounds so that I can boot cleanly. I really don't want to lose gvinum but I will if I have to.