From owner-freebsd-stable@FreeBSD.ORG Mon Feb 28 09:11:02 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0A87106564A for ; Mon, 28 Feb 2011 09:11:02 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from smtp-vbr1.xs4all.nl (smtp-vbr1.xs4all.nl [194.109.24.21]) by mx1.freebsd.org (Postfix) with ESMTP id 5532F8FC08 for ; Mon, 28 Feb 2011 09:11:01 +0000 (UTC) Received: from w2003s01.double-l.local (double-l.xs4all.nl [80.126.205.144]) by smtp-vbr1.xs4all.nl (8.13.8/8.13.8) with ESMTP id p1S8s959029129; Mon, 28 Feb 2011 09:54:10 +0100 (CET) (envelope-from Johan@double-l.nl) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 28 Feb 2011 09:54:09 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Message-ID: <57200BF94E69E54880C9BB1AF714BBCBDD318F@w2003s01.double-l.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.2-RELEASE - gmirror and gpart issue. Metadata overlap? Thread-Index: AcvV4VMJfEz+HZFETjm4osEy+epg0QBQjpVw References: <4D694336.3090203@yandex.ru> From: "Johan Hendriks" To: "Andrey V. Elsukov" X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: RE: 8.2-RELEASE - gmirror and gpart issue. Metadata overlap? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2011 09:11:03 -0000 On 26.02.2011 15:26, Marin Atanasov Nikolov wrote: >> After a reboot I get this right before the FreeBSD bootloader starts: >>=20 >> gptboot: invalid GPT backup header >>=20 >> I suppose this error simply means that gpart can't find it's backup=20 >> header, because gmirror and gpart both are using the last sectors for >> a provider to write it's metadata. >This message is from gptboot. Loader does not know about your software mirror and it just checks GPT headers in the second and last LBA. >As i see now, there is inconsistency in the behavior between gptboot and GEOM_PART_GPT. >gptboot does reading of GPT backup header from the last LBA, but GEOM_PART_GPT from the alternate LBA which is not equal to last LBA in your case. >> Which would mean that gmirror and gpart metadata overlap, and that's=20 >> why I see this message? >No. >> Anyway, I can still boot from the primary GPT header, and here's the=20 >> second message I get during boot: >>=20 >> GEOM: ad0: secondary GPT header is not in the last LBA. >>=20 >> Why does GEOM reports ad0, and not mirror/gm0 as the provider? I've=20 >> used the gmirror'ed device for gpart, not ad0. >This is how GEOM tasting works. Do you have any problem except for those messages? What does not work? >Also when you are writing problem report about gpart it will be not bad to add output of `gpart show` or `gpart list` commands. >And `gmirror list` for GEOM_MIRROR. I opened a discussion on this before the release. http://lists.freebsd.org/pipermail/freebsd-stable/2011-January/061184.ht ml On my 8.1 system, i get this message about the corrupt headers, but it booted on the 8.2 system it panics... I think a lot of people are going to get bit by this. As far as i know there is no warning anywhere that you can not use gpart and gmirror the whole disk. I also get this answer: << Maybe the boot process was made to be more standard-compliant :) >>> That is not the way it should work, well we make the boot process more standard compliant, bad luck for those who thougt it worked. I also convert back to normal partitioning and gmirror. Regards Johan =20