Date: Sat, 10 Jul 2004 10:34:58 +0200 From: Jens Schweikhardt <schweikh@schweikhardt.net> To: michael johnson <ahze@ahze.net> Cc: current@freebsd.org Subject: Re: Vinum and freebsd Message-ID: <20040710083458.GA3298@schweikhardt.net> In-Reply-To: <4D52DE9C-D20D-11D8-8E97-000A958C81C6@ahze.net> References: <4D52DE9C-D20D-11D8-8E97-000A958C81C6@ahze.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040710083458.GA3298>