Date: Sat, 12 Dec 2015 23:06:45 +0300 From: "Andrey V. Elsukov" <ae@FreeBSD.org> To: Ian Lepore <ian@freebsd.org>, Alexey Dokuchaev <danfe@FreeBSD.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r292058 - head/sbin/geom/class/part Message-ID: <566C7E55.2030303@FreeBSD.org> In-Reply-To: <1449944799.1358.160.camel@freebsd.org> References: <201512101037.tBAAbDMq065138@repo.freebsd.org> <1449767147.1358.62.camel@freebsd.org> <5669B969.5020605@FreeBSD.org> <20151212121209.GA60800@FreeBSD.org> <1449940829.1358.154.camel@freebsd.org> <566C6307.70200@FreeBSD.org> <1449944799.1358.160.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OP1CT7tL2OuldcwEDomDawu9Dit6xdXJf Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 12.12.15 21:26, Ian Lepore wrote: > On Sat, 2015-12-12 at 21:10 +0300, Andrey V. Elsukov wrote: >> On 12.12.15 20:20, Ian Lepore wrote: >>> I spent much of the last week fighting with "geom destroy" and >>> trying >>> to prevent the ressurection of old geoms during the creation of new >>> ones. It's a Big Mess and it doesn't really work well at all. I >>> came >>> to the conclusion that it's not geom destroy that needs a force >>> flag so >>> much as geom create, where it would mean "it is okay to replace any >>> existing geom with the new one." >> >> Let's be honest. This problem is completely unrelated to what I >> committed. >> >=20 > Oh yeah, totally. One of the first things I discovered about this > problem was that dd'ing some zeroes (where some < the whole device) > didn't help. But 'destroy -F' was mentioned in a panacea-like way, and= it's not really all that. 1. The goal of this patch is helping to users with recovering its GPT from damage. User must not know internals of GPT to work with it and they don't know. If you position yourself as power user and you think that dd will do what you want, just continue use it. But as power user you should know and now you know what you need overwrite using dd to destroy GPT. Just another one sector in the end of the disk. 2. All problems that you described in previous messages was related to MBR+BSD label. FreeBSD uses native GPT without any nested partitioning tables, and described problems aren't related to GPT. 3. You are criticizing the change that doesn't affect you, so what you want? Do you want to revert this change? Ok, feel free to do it. Personally, I can recover or just recreate my partition tables without this change. The change was done, because several users asked me to do it= =2E > I don't think I'll bother to reply to the rest, since it seemed to be > saying basically "raw data is available to you and beyond that this > stuff is supposed to be hard to work with". --=20 WBR, Andrey V. Elsukov --OP1CT7tL2OuldcwEDomDawu9Dit6xdXJf 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/ iQEcBAEBCAAGBQJWbH5VAAoJEAHF6gQQyKF6LpAH/jZEgsPtbRJz+K/oFgp2+wfL YSN9YWYEb7o6VFLCK5bPqLjh5ZC9j+Q7C8urF/NeS3GYpX/6gNP/AQVAYvTAQh3t qeUlpOnSpaamCDnuVdadhYsRDJ9zwWMzrHc+Feu0LQjDmCHISSNm+LI9QYFripkh Li5KvGlQ8iRFQWoOcx8evjLsa2UugKgO/uz2KPB/KIaFviRejJqDc2bhKsXJhx5C 4qy71IEslG4Mg1kYdgoiGEAhA8j3s+sHMpPuAxE+iFwSHfIV4V/+dhueNpDafKwK 7IkfZvGoyObxrkimmDfNlpz1v1EOrAw47ZGpid+gl7aeZqlbz9/8n3ZgG6wch+Q= =B6sV -----END PGP SIGNATURE----- --OP1CT7tL2OuldcwEDomDawu9Dit6xdXJf--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?566C7E55.2030303>