From owner-freebsd-stable@FreeBSD.ORG Wed Nov 24 09:33:59 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3C9316A4CE for ; Wed, 24 Nov 2004 09:33:59 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 375D443D5F for ; Wed, 24 Nov 2004 09:33:59 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id E0329ACBCF; Wed, 24 Nov 2004 10:33:56 +0100 (CET) Date: Wed, 24 Nov 2004 10:33:56 +0100 From: Pawel Jakub Dawidek To: Michael Reifenberger Message-ID: <20041124093356.GJ7232@darkness.comp.waw.pl> References: <20041124091400.G74665@fw.reifenberger.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XlS4q8O07AKt4+K1" Content-Disposition: inline In-Reply-To: <20041124091400.G74665@fw.reifenberger.com> 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-stable@FreeBSD.org Subject: Re: graid3 not working on partitions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 09:33:59 -0000 --XlS4q8O07AKt4+K1 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 24, 2004 at 09:20:33AM +0100, Michael Reifenberger wrote: +> Hi, +> since GEOM so a nicely layered framework (and I didnt want to loose my M= BR) +> I tried to setup a graid3 using using da1s1a... instead of da1... +> getting the following negative results: +> (not only trying to use da1/da1s1 for parity, +> it trashes the disklabel on da1s1 too) +>=20 +> ... +> (totum)(root) graid3 label -r -v data da3s1a da4s1a da1s1a +> GEOM_RAID3: Device data created (id=3D224). +> GEOM_RAID3: Device data: provider da3s1a detected. +> Metadata value stored on da3s1a. +> GEOM_RAID3: Device data: provider da4s1a detected. +> Metadata value stored on da4s1a. +> GEOM_RAID3: Device data: provider da1 detected. The thing you have to avoid (probably it should be more clear in the manual page) is to allow providers to share the same last sector. The gradi3 class uses the last provider's sector to store metadata and if you have 2 or more providers which share this sector you are in troubles. In your case da1, da1s1 and da1s1a providers use the same last sector and graid3 is confused and picks first provider given by GEOM for taste. You should create labels once again and leave the last sector on da1s1 unused, so da1s1 and da1s1a don't end at the same offset. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --XlS4q8O07AKt4+K1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBpFWEForvXbEpPzQRAm6mAJ4weSTauo+kIfm/KNJizl+5ul65nwCeI6iG UVCCu42ZCXiNVfluJJvCb0M= =17As -----END PGP SIGNATURE----- --XlS4q8O07AKt4+K1--