Date: Mon, 29 Nov 2004 16:11:27 +0100 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Jo?o Carlos Mendes =?iso-8859-2?Q?Lu=EDs?= <jonny@jonny.eng.br> Cc: freebsd-hackers@freebsd.org Subject: Re: Hand on gmirror (Was: Re: gmirror bugs, how many?) Message-ID: <20041129151127.GN7232@darkness.comp.waw.pl> In-Reply-To: <41AB37B8.7060303@jonny.eng.br> References: <41A4FD60.4050501@jonny.eng.br> <20041125224547.GB7232@darkness.comp.waw.pl> <41A6B76F.4020101@jonny.eng.br> <20041126082340.GC7232@darkness.comp.waw.pl> <41A78A47.3050309@jonny.eng.br> <20041128202759.GF7232@darkness.comp.waw.pl> <41AB37B8.7060303@jonny.eng.br>
next in thread | previous in thread | raw e-mail | index | archive | help
--9H9VVCLI5QJPfUsZ Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 29, 2004 at 12:52:40PM -0200, Jo?o Carlos Mendes Lu=EDs wrote: +> >+> Indeed, the -h option is what I wanted and the "bug" is in the= =20 +> >+> manual. What would happen if I change the disc ID in this case? +> > +> >Your disk will not be detected as a mirror component, because hardcoded +> >name is different. +>=20 +> Oops. Is there a check for that? For example, let's say that ad0s1 got= =20 +> renamed to ad1s1, and hardcoded a reference to ad0s1. In this case,=20 +> there is a disk called ad0s1 in the system. Is gmirror smart enough in= =20 +> this case? In this case ad1s1 will not be connected to the mirror (but don't worry, ad0s1 will not be connected as well). +> >+> sigesc::root jcmendes [553] disklabel mirror/vol0 +> >+> # /dev/mirror/vol0: +> >+> 8 partitions: +> >+> # size offset fstype [fsize bsize bps/cpg] +> >+> a: 16498864 16 unused 0 0 +> >+> c: 16498880 0 unused 0 0 # "raw" part= ,=20 +> >+> don't edit +> >+> sigesc::root jcmendes [554] +> >+>=20 +> >+> Seems good until now. Except for the offset 16 of the "a" partiti= on.=20 +> >+> Is this necessary? The man page says that the only sector reserved= =20 +> >+> for metadata is the provider's last one. +> > +> >Ehh, "blame" disklabel(8). First 16 sectors are reserved for boot code. +>=20 +> And why this does not happen with ad0s1, etc? I think it should, only using sysinstall for this will not allocate those sectors. Anyway, it has nothing to do with gmirror. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --9H9VVCLI5QJPfUsZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBqzwfForvXbEpPzQRAs7JAKCEXY6fr8cR0DPRTOxPSFbcpsepUwCg0GO7 q8RyX3VaibwJ+8je/KJcyRM= =qucQ -----END PGP SIGNATURE----- --9H9VVCLI5QJPfUsZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041129151127.GN7232>