From owner-freebsd-current@freebsd.org Wed Sep 28 18:10:52 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1ACFAC01E40 for ; Wed, 28 Sep 2016 18:10:52 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward3j.cmail.yandex.net (forward3j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 94666147F; Wed, 28 Sep 2016 18:10:51 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1h.mail.yandex.net (smtp1h.mail.yandex.net [84.201.187.144]) by forward3j.cmail.yandex.net (Yandex) with ESMTP id D0DDE20BEE; Wed, 28 Sep 2016 21:10:48 +0300 (MSK) Received: from smtp1h.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1h.mail.yandex.net (Yandex) with ESMTP id A17F68C0927; Wed, 28 Sep 2016 21:10:44 +0300 (MSK) Received: by smtp1h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id FXWiMXjPIU-Ai0auww8; Wed, 28 Sep 2016 21:10:44 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1475086244; bh=kyDK9DrlWjVboRdXhwRDyX05wOg0MxUCxZDdKQczYWY=; h=Subject:To:References:Cc:From:Message-ID:Date:In-Reply-To; b=A3dYjtulhKSVqCkhgCVkCq+CWLEifDRabiKiCzq5vsqu0vNgTH6daqvMKLfQnkiEz sqfXrx1xnvWITgO4uRTj7vNM0MfGVuN6ZQB55OgzEh1DY0cYdrYJckRCnEfLPRDGzj 1MPIc88j6f3yDsYW9x+v2LKOe9mLJiItC2lDrfd4= Authentication-Results: smtp1h.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0,1 0 Subject: Re: Destroy GPT partition scheme absolutely, how? To: John Baldwin , freebsd-current@freebsd.org References: <20160926150109.0d0d793e@hermann> <57E92726.2020605@gmail.com> <5484D815-4B17-456B-BA60-CC6F4E97AFE3@gmail.com> <1785064.lgVzRW13Wf@ralph.baldwin.cx> Cc: Ngie Cooper , Ernie Luzar , "Hartmann, O." From: "Andrey V. Elsukov" Message-ID: Date: Wed, 28 Sep 2016 21:08:34 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <1785064.lgVzRW13Wf@ralph.baldwin.cx> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="f81KM58258ob6VDDO4klCKCDSiik0UjRO" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 28 Sep 2016 18:10:52 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --f81KM58258ob6VDDO4klCKCDSiik0UjRO Content-Type: multipart/mixed; boundary="PuhroITUpP9DiKi0dCn6PBebtNpvsgvCQ"; protected-headers="v1" From: "Andrey V. Elsukov" To: John Baldwin , freebsd-current@freebsd.org Cc: Ngie Cooper , Ernie Luzar , "Hartmann, O." Message-ID: Subject: Re: Destroy GPT partition scheme absolutely, how? References: <20160926150109.0d0d793e@hermann> <57E92726.2020605@gmail.com> <5484D815-4B17-456B-BA60-CC6F4E97AFE3@gmail.com> <1785064.lgVzRW13Wf@ralph.baldwin.cx> In-Reply-To: <1785064.lgVzRW13Wf@ralph.baldwin.cx> --PuhroITUpP9DiKi0dCn6PBebtNpvsgvCQ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 26.09.2016 23:51, John Baldwin wrote: >> Why not just use "gpart destroy -F provider"? >=20 > That doesn't always work. In particular, if a disk was partitioned wit= h GPT > and then you use normal MBR on it afterwards, the 'gpart destroy -F' of= the > MBR will leave most of the GPT intact and the disk will come up with th= e old > GPT partitions, not as a raw disk. If you would did `gpart destroy -F` for GPT, then it would not have appeared again. This is very strange problem, how did you created MBR if you have not destroyed GPT? :) After this commit it seems very unlikely to reproduce https://svnweb.freebsd.org/base?view=3Drevision&revision=3D292057 Described problem can be reproduced with BSD label. --=20 WBR, Andrey V. Elsukov --PuhroITUpP9DiKi0dCn6PBebtNpvsgvCQ-- --f81KM58258ob6VDDO4klCKCDSiik0UjRO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEvBAEBCAAZBQJX7AcmEhxidTdjaGVyQHlhbmRleC5ydQAKCRABxeoEEMiheutP B/0WikuAzS8p6EXsqh+nSPIGQVt1ZtMLCVoxiqyxyYNOV18KfTWWJSgli6tomh4m Nu0GG+rUjbl2eP6dcQDSxqQBOtVRivgL1PmEWbTe6cD24Kv77SUh1PHtHxrC5F6C iT2wPUf7XJpT+zjWE1j78wUKqLKgE6N1wOWc/RactAJPqvpy4fASJDCMmeUr7WXs pJyDxgRkHbNDw1PuLugx67RYkJqfVHAKFsk6QdsFJdPI1o9VrEyRlUo39xBj04Hr KjIVlC47z0GTUX5SH1gOnD7ef2zE59IhAqBgpjeExeBpe51lixK1/sgnh/Ddd6Ev xvzS6g60x8ceMqgmLtGpsGku =uYkw -----END PGP SIGNATURE----- --f81KM58258ob6VDDO4klCKCDSiik0UjRO--