Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Nov 2004 20:32:30 +0100
From:      Pawel Jakub Dawidek <pjd@FreeBSD.org>
To:        Ivan Voras <ivoras@fer.hr>
Cc:        freebsd-geom@freebsd.org
Subject:   Re: Big geom_raid3 problems
Message-ID:  <20041123193230.GH7232@darkness.comp.waw.pl>
In-Reply-To: <41A384FE.1070002@fer.hr>
References:  <41A384FE.1070002@fer.hr>

next in thread | previous in thread | raw e-mail | index | archive | help

--sdJFN6SSISdF2ksn
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 23, 2004 at 07:44:14PM +0100, Ivan Voras wrote:
+> Im trying to use graid3 in production but I've encountered a big problem:
+>=20
+> I'm creating raid3 volume from three discs: ad4, ad5, ad6. All is well=
=20
+> (and I mean everything - removing, inserting, rebuilding the raid=20
+> device, using a filesystem on it) until I write BSD disk label on the=20
+> raid volume (/dev/raid3/geri3). At that time, it seems to write partial=
=20
+> labels to each of the data drives (like it should, presumably, since it=
=20
+> splits requests), but FreeBSD recognizes it! e.g. /dev/ad4a, /dev/ad4b,=
=20
+> etc. This by itself wouldn't be bad, but it seems to confuse the hell=20
+> out of geom_raid3. Here are the messages that it writes on subsequent=20
+> boot or loading:
[...]

This problem has been fixed in HEAD and should be MFCed soon.

+> Also, at one time, I accidentally wrote a disklabel to /dev/ad4 instead=
=20
+> of the raid volume, and it suceeded, though geom_raid3 detected it and=
=20
+> started synching the provider. Shouldn't the devices be locked or someth=
ing?

If it is not opened, it is not protected. If you create a file system on
it and you mount this file system this should not be possible anymore.

--=20
Pawel Jakub Dawidek                       http://www.FreeBSD.org
pjd@FreeBSD.org                           http://garage.freebsd.pl
FreeBSD committer                         Am I Evil? Yes, I Am!

--sdJFN6SSISdF2ksn
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFBo5BOForvXbEpPzQRAj44AKDsZRTxU0Y4/u54bdpuJ7W7FTZ2UQCbBvNS
VGh3kWxcIaMeXLJA7Nplhw8=
=Hd6x
-----END PGP SIGNATURE-----

--sdJFN6SSISdF2ksn--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041123193230.GH7232>