From owner-freebsd-current@FreeBSD.ORG Sat Jul 10 08:34:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04DD916A4CE for ; Sat, 10 Jul 2004 08:34:57 +0000 (GMT) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1372B43D2D for ; Sat, 10 Jul 2004 08:34:56 +0000 (GMT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 433B03B916; Sat, 10 Jul 2004 10:34:54 +0200 (CEST) Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) i6A8YwfC003478; Sat, 10 Jul 2004 10:34:58 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost)i6A8YwBZ003477; Sat, 10 Jul 2004 10:34:58 +0200 (CEST) (envelope-from schweikh) Date: Sat, 10 Jul 2004 10:34:58 +0200 From: Jens Schweikhardt To: michael johnson Message-ID: <20040710083458.GA3298@schweikhardt.net> References: <4D52DE9C-D20D-11D8-8E97-000A958C81C6@ahze.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D52DE9C-D20D-11D8-8E97-000A958C81C6@ahze.net> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: Vinum and freebsd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 08:34:57 -0000 On Fri, Jul 09, 2004 at 09:05:58PM -0400, michael johnson wrote: # Hi, # I've had problems with vinum and newer 5.2-CURRENT kernels, I am # unable to boot a newer kernel with out the kernel going in to a panic # and saying "panic: umount: dangling vnode" . I've had this problem # since early June and it doesn't seemed to be fixed (as of July 9th) , # has something changed in vinum that I am missing and I need to change # about my setup or is vinum just broken right now? Yes, it's broken for a particular setup, it appears. There is at least a handful of people with the "dangling vnode" panic. For others there is no problem at all. It has not yet been identified why it happens only to some, but there is a hint on which revisions you need to back out to make vinum work again in the thread "panic with vinum". Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped)