How to safely remove rest of GTP?

Ian Lepore ian at freebsd.org
Mon Jan 30 17:23:29 UTC 2017


On Mon, 2017-01-30 at 19:09 +0300, Andrey V. Elsukov wrote:
> On 30.01.2017 18:55, Warren Block wrote:
> > 
> > > 
> > > > 
> > > > GEOM: da6: the primary GPT table is corrupt or invalid.
> > > > GEOM: da6: using the secondary instead -- recovery strongly
> > > > advised.
> > > > GEOM: da22: the primary GPT table is corrupt or invalid.
> > > > GEOM: da22: using the secondary instead -- recovery strongly
> > > > advised.
> > > > GEOM: da6: the primary GPT table is corrupt or invalid.
> > > > GEOM: da6: using the secondary instead -- recovery strongly
> > > > advised.
> > > > GEOM: da22: the primary GPT table is corrupt or invalid.
> > > > GEOM: da22: using the secondary instead -- recovery strongly
> > > > advised.
> > > You may try attached patch, I did only basic tests, so first try
> > > somewhere :)
> > I really like the idea of gpart being able to remove the secondary
> > GPT,
> > but combining it with the existing destroy command is
> > ambiguous.  It's
> > hard for the user to tell what will happen, and the command itself
> > implies that it will destroy all partitioning.
> I don't see any ambiguity here. A user sees corrupted GPT, it can
> only 
> destroy or recover it. It is impossible to have a corrupted GPT and
> some 
> other type of partition table in the same time. So, if you use
> 'gpart 
> destroy' - you want to explicitly destroy it.
> 

The question to ask here is why are you the only one who can't see or
understand that a user is NOT going to use a "destroy" command on a
 disk containing live data?  Especially given the confusing vagueness
of the gpart docs.

-- Ian



More information about the freebsd-hackers mailing list