Re: aliasing (or renaming) kern.geom.debugflags

On Fri, Oct 7, 2011 at 12:03 PM, Poul-Henning Kamp <phk@xxxxxxxxxxxxxx> wrote:
In message <alpine.BSF.2.00.1110071236270.2450@xxxxxxxxxxx>, Warren Block write
s:

Which is the exactly right question to ask.

The procedure documented is clearly flawed.


Well, yes.  The goal is to unprotect the device, regardless of what may
already be on it.  Then the user can overwrite it with the memory stick
image.

Unprotect from what ?  from being already mounted ?

If you cannot open a geom provider for writing, then it is because
some piece of code in the kernel thinks it already owns the device
and don't want you to muck about with it.

Overriding this check is just asking for panics...


What I usually do in cases like this is:

       (umount /dev/${whatever} || true) > /dev/null 2>&1

And if that isn't enough, or not possible, then the user needs
to undo whatever he did to the device...

My guess is that GEOM isn't letting go of the GPT table and you have
multiple partitions in the GPT table and you're not destroying them
hierarchically in a proper manner.. but again, that's just a guess
based on hazy recollection.
-Garrett
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"