From owner-freebsd-geom@FreeBSD.ORG Thu Mar 13 18:00:33 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AC531065670 for ; Thu, 13 Mar 2008 18:00:33 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id BF6B48FC19 for ; Thu, 13 Mar 2008 18:00:32 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 15069 invoked by uid 2001); 13 Mar 2008 18:00:31 -0000 Date: Thu, 13 Mar 2008 12:00:31 -0600 From: "Rick C. Petty" To: Damian Wiest Message-ID: <20080313180031.GA14969@keira.kiwi-computer.com> References: <20080307230058.GA8902@keira.kiwi-computer.com> <20080308024954.GF15859@dfwdamian.vail> <20080308064455.GA13341@keira.kiwi-computer.com> <20080313001232.GL32089@dfwdamian.vail> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080313001232.GL32089@dfwdamian.vail> User-Agent: Mutt/1.4.2.3i Cc: freebsd-geom@freebsd.org Subject: Re: geom_vinum platform-independent brokenness X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Mar 2008 18:00:33 -0000 On Wed, Mar 12, 2008 at 07:12:32PM -0500, Damian Wiest wrote: > > I was just thinking of the simplest case where the disk you're moving > used a bsdlabel. Ok. > > I'm not talking about the disklabel here. geom_vinum takes up the first > > 265 sectors (512 bytes each) to store its configuration. These are > > straight-up disks that aren't needed in Windoze or other OS-- just plain > > FreeBSD, so we use the full disks without labels or MBR partitions. > > Right. I was just wondering what would need to be changed when moving > a bsdlabeled disk from x86 to amd64 or vice-versa. I was thinking that > if the labels (both bsdlabel and gvinum's) were padded a bit at the end > (so you don't clobber any real data), then one could simply rewrite the > label once the disk was moved to the new system. My thinking was that > it might be simpler to allow the label to be rewritten with some utility > versus modifying how gvinum interprets labels. geom_vinum has nothing to do with bsdlabels. There is extra padding at the beginning of the vinum configuration to allow for an MBR and/or a bsdlabel. Because gvinum uses GEOM's tasting, all providers are searched for vinum configuration.. It shouldn't matter whether you have a bsdlabel or not; geom_vinum just seeks to byte 4096 into each provider and checks for the magic. > No, I wasn't saying anything about UFS in particular. Just that you'll > also want to consider the underlying filesystems and not just the gvinum > bits. *My* concern is the gvinum bits. UFS seems to work for me, other file systems are beyond the scope of this personal project. -- Rick C. Petty