Re: Vinum and freebsd

Hi,
	I noticed I did something wrong when I made the vinum partition, which 
I created well over a year ago,  is that I did not follow the 
directions correctly by using bsdlabel (disklabel) and changing the 
partition type from 4.2BSD to vinum. I changed 4.2BSD to vinum today 
hoping that would fix the problem but it did not and I got a kernel 
panic.

Could this have anything to do with the problem I and a few other 
people are having with their vinum setups is that we didn't follow the 
directions when creating the vinum partition and not changing the 
partition type to vinum before creating the partition?

Michael


On Jul 10, 2004, at 4:34 AM, Jens Schweikhardt wrote:

> 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)
>