From owner-freebsd-current@FreeBSD.ORG Fri Nov 21 16:49:15 2003 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 77CA216A4CE for ; Fri, 21 Nov 2003 16:49:15 -0800 (PST) Received: from marklar.blazingdot.com (marklar.blazingdot.com [207.154.84.83]) by mx1.FreeBSD.org (Postfix) with SMTP id 3EAFD43FBF for ; Fri, 21 Nov 2003 16:49:14 -0800 (PST) (envelope-from marcus@blazingdot.com) Received: (qmail 95948 invoked by uid 503); 22 Nov 2003 00:49:14 -0000 Date: Fri, 21 Nov 2003 16:49:14 -0800 From: Marcus Reid To: Greg 'groggy' Lehey Message-ID: <20031122004914.GB91890@blazingdot.com> References: <20031121234212.GA91890@blazingdot.com> <20031122003538.GP32267@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031122003538.GP32267@wantadilla.lemis.com> X-Coffee-Level: nearly-fatal User-Agent: Mutt/1.5.4i cc: freebsd-current@freebsd.org Subject: Re: Vinum breakage - please update UPDATING 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, 22 Nov 2003 00:49:15 -0000 Hi Greg, On Sat, Nov 22, 2003 at 11:05:38AM +1030, Greg 'groggy' Lehey wrote: > On Friday, 21 November 2003 at 15:42:12 -0800, Marcus Reid wrote: > > Hello, > > > > I just upgraded a -CURRENT box this afternoon to discover that vinum > > is broken. If I hadn't done dumps of my working world beforehand I > > would be in pretty sad shape. Should UPDATING make note of this > > breakage? > > No. UPDATING is for things that will change relatively permanently. Ah, OK. Thanks; I had no idea how long it was expected to be broken. > > It would have saved me some embarassment, and I'm sure others are > > about to clobber their machines. > > As far as I can tell, this breakage doesn't harm the data. Others > have reported that it works on older versions of CURRENT. I hope to > have it fixed this weekend. FYI, it didn't destroy any data. vinum dumpconfig reported everything was fine, but there was no mount point in /dev/vinum. When I reverted to an earlier -CURRENT snapshot, it worked without a hitch. Thanks for the response; I should not have shouted so loudly about updating UPDATING. I just wish I had read the CURRENT list before shooting myself in the foot. Sincerely, Marcus > > Greg > -- > See complete headers for address and phone numbers.