From owner-freebsd-current@FreeBSD.ORG Fri Aug 6 11:49:37 2004 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 A493B16A4CE for ; Fri, 6 Aug 2004 11:49:37 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CCDB43D2F for ; Fri, 6 Aug 2004 11:49:37 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id A818DACAF1; Fri, 6 Aug 2004 13:49:35 +0200 (CEST) Date: Fri, 6 Aug 2004 13:49:35 +0200 From: Pawel Jakub Dawidek To: Sam Lawrance Message-ID: <20040806114935.GD628@darkness.comp.waw.pl> References: <1091792300.749.14.camel@dirk.no.domain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a2FkP9tdjPU2nyhF" Content-Disposition: inline In-Reply-To: <1091792300.749.14.camel@dirk.no.domain> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: current@FreeBSD.org Subject: Re: geom stripe/concat metadata suggestion 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: Fri, 06 Aug 2004 11:49:37 -0000 --a2FkP9tdjPU2nyhF Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 06, 2004 at 09:38:21PM +1000, Sam Lawrance wrote: +> Would it be a good idea to store the device name, or something similar, +> in the metadata? +>=20 +> For example, if I have a disk divided like this: +>=20 +> |--------------ad0--------------| +> |-------------ad0s1-------------| +> |----ad0s1g-----|-----ad0s1d----| +>=20 +> The metadata is written into the last sector, so when the stripe/concat +> classes are tasting they can't work out whether it belongs to ad0s1d, +> ad0s1 or ad0. +>=20 +> I've had problems creating stripes and concats with this configuration. Yes, this is a problem, but I'm not going to store provider's name in the metadata, because now, you just copy disk with 'dd' and your stripe still works. As a workaround you shouldn't use last sector on ad0s1d. If you don't want to change partition, you can use gnop(8) for this: # gstripe clear ad0s1d # gnop create -s `diskinfo ad0s1d | awk '{print $3 - 512}'` ad0s1d # gstripe label ad0s1d.nop But in such case it will not be automatically discovered at boot time. The best solution probably is to not use last disk sector... Hmm, when such conflict is detected I should probably destroy whole device, instead of configuring it from first component found. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --a2FkP9tdjPU2nyhF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBE3BPForvXbEpPzQRArvqAJsEjGwL9aAmWJMhyKB31IzYq0KTAgCg0DCf 9M7iPBW68J0wi5GpbLdCQTg= =xpgH -----END PGP SIGNATURE----- --a2FkP9tdjPU2nyhF--