Re: Problems with corrupted vinum devices...

At 5:44 PM +0100 2001/1/5, [EMAIL PROTECTED] wrote: > diff -ru /tmp/vinum/vinumvar.h ./vinumvar.h > --- /tmp/vinum/vinumvar.hMon May 22 18:21:37 2000 > +++ ./vinumvar.h Thu Jan 4 19:12:01 2001 > @@ -158,15 +158,15 @@ >* probably too small. >*/ > > -INITIAL_DRIVES = 4, >

Re: Problems with corrupted vinum devices...

At 5:44 PM +0100 2001/1/5, [EMAIL PROTECTED] wrote: > I suggest increasing INITIAL_DRIVES in vinumvar.h to avoid array > resize and the associated race conditions. When I tried to configure > vinum to use 14 disks yesterday, the machine immediately crashed with > a trap 12 in response to 'vi

Re: Problems with corrupted vinum devices...

> However, at some point within the next couple of hours (we're not > quite sure when), the machine crashed, and vinum failed to come up on > the reboot. We had to comment out the /etc/fstab entries that > referred to the vinum volumes, and since then have been trying to > debug the pro

Problems with corrupted vinum devices...

Folks, I've read the man page, the vinum debugging page at , searched the archives of the stable mailing list, and still haven't found anything that would appear to address the situation we've just started experiencing. Many mo