Date: Wed, 02 Mar 2022 06:45:45 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262241] gpart(8) destroy: option -F seems to not effectively destroy all partitions in some situations Message-ID: <bug-262241-227-BDiVy4Z28d@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262241-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262241-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262241 Stefan B. <sblachmann@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sblachmann@gmail.com --- Comment #3 from Stefan B. <sblachmann@gmail.com> --- Hmm. So "gpart destroy -F geom" does _not_ actually wipe the partition block, at least if it is a MBR one. Now I think I understand that strange error that I encountered when attempt= ing to create a clone on a (formerly) MBR partitioned USB stick while testing my new Skunk Cloner (https://github.com/SkunkOS/SkunkCloner). If gpart destroy does _not_ work under some configurations, the only work-around to ensure clean partition data then would be to zero-dd the partition table. Honestly, I would rather prefer to be able to use gpart destroy to clear out any old partition data! I don't like having no other choice than to hackingly use dd to clear parti= tion data. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262241-227-BDiVy4Z28d>