From owner-freebsd-current Fri Oct 4 20:49:30 2002 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 A472E37B401; Fri, 4 Oct 2002 20:49:29 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAAA343E42; Fri, 4 Oct 2002 20:49:28 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g953mxOo076525; Fri, 4 Oct 2002 23:49:00 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 4 Oct 2002 23:48:59 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ian Dowse Cc: n0go013 , "Greg 'groggy' Lehey" , current Subject: Vinum now working with GEOM (was: Re: [ GEOM tests ] disklabel warnings and vinum drives lost ) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 4 Oct 2002, Robert Watson wrote: > > This turns out to be vinum doing a DIOCWLABEL to make the label writable > > before writing its configuration, but GEOM does not support that ioctl I > > presume. It should be safe to ignore these DIOCWLABEL ioctl return > > values as the actual writing of the vinum data should give a suitable > > error if making the label writable fails and is important. The patch > > below is Robert's patch with all 3 other issues fixed, and together, > > this seems to be enough to make vinum work again. > > Ok -- I went ahead and booted and ran the merged patch on my testbox, > and Vinum is up and running fine with GEOM. I think we're set to commit > -- do you want to, or shall I? Ok -- it appears to work in my environment also, so at a first glance, it looks like Vinum is working properly with GEOM. I've committed the various patches to the CVS repository, so anyone interested in experimenting to make sure it works for them also can sync up and give it a try. The usual warnings about data integrity with pre-production software apply :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message