From owner-freebsd-questions Wed Mar 3 19:41:14 1999 Delivered-To: freebsd-questions@freebsd.org Received: from inet.chip-web.com (c1003518-a.plstn1.sfba.home.com [24.1.82.47]) by hub.freebsd.org (Postfix) with SMTP id 7F24115065 for ; Wed, 3 Mar 1999 19:40:27 -0800 (PST) (envelope-from ludwigp@bigfoot.com) Received: (qmail 900 invoked from network); 4 Mar 1999 03:40:09 -0000 Received: from speedy.chip-web.com (HELO speedy) (172.16.1.1) by inet.chip-web.com with SMTP; 4 Mar 1999 03:40:09 -0000 Message-Id: <4.1.19990303193018.00a54c80@mail-r> X-Sender: ludwigp2@mail-r X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 03 Mar 1999 19:38:24 -0800 To: Darryl Okahata , Greg Lehey , freebsd-questions@FreeBSD.ORG From: Ludwig Pummer Subject: Re: CCD vs vinum Cc: dillon@apollo.backplane.com In-Reply-To: <19990304124337.X441@lemis.com> References: <199903031840.KAA02285@mina.sr.hp.com> <199903031840.KAA02285@mina.sr.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:13 PM 3/3/99 , Greg Lehey wrote: >> How serious are the vinum bugs? > >Vinum is a much larger package than ccd. To the best of my knowledge, >the part of vinum which corresponds to ccd is bug-free. The bugs in >vinum are mainly of the shoot-yourself-in-the-foot variety, and >they're in the area of configuration management, which ccd doesn't >have. Configuration bugs like having two vinum volumes overlapping...I just shot myself in the foot by having a /usr2 and /var2 which overlapped. I didn't notice until when I rebooted and vinum kept complaining about "size -1b" and other things (I won't quote them because I've already obliterated the vinum config). I tried to wring every last sector out of my partition...guess I'll have to try (later...&#*$ homework now) with more conservative volume sizes. Just my $0.02 --Ludwig Pummer ( ludwigp@bigfoot.com ) ICQ UIN: 692441 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message