From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 13:38:28 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 67F5D16A4CE; Mon, 29 Nov 2004 13:38:28 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF97C43D5D; Mon, 29 Nov 2004 13:38:27 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id C4972ACAFB; Mon, 29 Nov 2004 14:38:25 +0100 (CET) Date: Mon, 29 Nov 2004 14:38:25 +0100 From: Pawel Jakub Dawidek To: Chris Hedley Message-ID: <20041129133825.GL7232@darkness.comp.waw.pl> References: <20041127193532.X15946@teapot.cbhnet> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Gnkm4uF329L9IN0W" Content-Disposition: inline In-Reply-To: <20041127193532.X15946@teapot.cbhnet> 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: freebsd-current@freebsd.org cc: marcel@freebsd.org Subject: Re: GEOM: gpt partitions on a gmirror array possible? 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: Mon, 29 Nov 2004 13:38:28 -0000 --Gnkm4uF329L9IN0W Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 27, 2004 at 07:58:35PM +0000, Chris Hedley wrote: +> Hi all, +>=20 +> A hopefully quick question! I have looked for a solution for (or=20 +> discussion about) this, if I've just failed to find it, please point me = in=20 +> the right direction. +>=20 +> This is what I'm trying to do: I've created a RAID-1 array, m1, using=20 +> gmirror on two scsi units, da0 and da1, and I'd like to chop it up into= =20 +> logical partitions using gpt, as I understand (correctly, hopefully) the= re=20 +> are leanings toward gpt rather than bsdlabel as being the correct way to= =20 +> do things. Now when I initialise and create my gpt partition on=20 +> mirror/m1, I get no new entries in /dev/mirror but I _do_ get separate= =20 +> /dev/da0p1 and /dev/da1p1 entries appearing. I've probably completely= =20 +> failed to understand the whole concept of GEOM tasting and unprejudiced= =20 +> hierarchy and so on as I decided I may as well try to create my UFS2=20 +> filesystem on /dev/da0p1 in /dev/mirror/m1p1's absence and see if=20 +> /dev/da1p1 magically follows suit. Needless to say it doesn't, I just e= nd=20 +> up with a dirty RAID-1 disc that needs resynchronising, with da0p1=20 +> (un)mysteriously disappearing after the newfs. +>=20 +> Is there a correct way to do this, or am I once again guilty of trying t= o=20 +> use something that isn't quite ready yet? Perhaps I should do it the=20 +> other way around and use gpt first and create one gmirror per partition;= =20 +> that solution didn't "feel" right for some reason, but I can't really=20 +> quantify that particularly as, if I understand the GEOM documentation=20 +> correctly, multiple gmirrors with their respective paritions on the same= =20 +> set of discs shouldn't compete with each for access. +>=20 +> My system is FreeBSD/amd64, 6.0-current (Oct 25th vintage) using ahc for= =20 +> my test scsi discs and aac for my active discs. It is because GEOM_GPT class only allow to create GPT labels on rank#1 providers (i.e. disks). I'm not sure why we have this hack, maybe marcel@ knows something more (cc'ed). --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --Gnkm4uF329L9IN0W Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBqyZRForvXbEpPzQRAhgSAKCPgwYs4PwT6KcaepgxWoRPQczJxgCcCVnt hLeVVz+ToYjPmCor5zR4b7M= =Eb4i -----END PGP SIGNATURE----- --Gnkm4uF329L9IN0W--