Date: Fri, 14 Jun 2013 10:46:51 +0200 From: Alban Hertroys <haramrae@gmail.com> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: Johan Hendriks <joh.hendriks@gmail.com>, Kimmo Paasiala <kpaasial@gmail.com>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: zpool labelclear destroys GPT data Message-ID: <CAF-3MvNcu2fr_z%2BJ49YV2sn1mHAnn7xqTcOGSpei8hMhvBr1OA@mail.gmail.com> In-Reply-To: <B92714FF-CE1A-44B8-9284-C12429FA42D7@gsoft.com.au> References: <51B9BB14.6020103@gmail.com> <CA%2B7WWSdrS2QYKe8-w31dnxYRriYbhYjj_dwOjhXtTvSsh8Cisw@mail.gmail.com> <51BA381C.8070900@gmail.com> <CA%2B7WWSdsZaEQjWPBeuXb-AGpERqvjw2koZVjyEx5ah8TJTB1KA@mail.gmail.com> <51BAC7D1.70208@gmail.com> <0A53B6AA-9614-42E9-8AA1-82233426EEE6@gsoft.com.au> <CAF-3MvOtM6%2Bk1bOWLUMY_-zmWCWbX98hGhj8kTJsWURTKEZxPQ@mail.gmail.com> <B92714FF-CE1A-44B8-9284-C12429FA42D7@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14 June 2013 10:21, Daniel O'Connor <doconnor@gsoft.com.au> wrote: > > On 14/06/2013, at 17:48, Alban Hertroys <haramrae@gmail.com> wrote: > > IMHO it would be helpful to verify what's there first and warn the user > about it if such an operation will overwrite a different type of label than > what is about to get written there. > > Perhaps it should even refuse to write (by issuing an error stating that > there is already a label there - and preferably also what type) until the > label that's already there gets explicitly cleared by the user or until the > command gets forced. > > Does that make sense? > > The problem with this is that then each label tool needs to know about > every other label format you want to detect for.. > Isn't it possible to add such information to labels, so that the tools at least know "who" to ask what they're dealing with? > > If a label format has a checksum then you could ignore a request to nuke > the label if there is no valid checksum (with a flag to force). No idea how > many have checksums though.. > If there is no guaranteed method of identifying "data" on the disk as a label, then you can't warn the user in all cases. That's not particularly helpful for those cases where you can't warn the user. That's possibly a worse situation than what started this thread. -- If you can't see the forest for the trees, Cut the trees and you'll see there is no forest.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF-3MvNcu2fr_z%2BJ49YV2sn1mHAnn7xqTcOGSpei8hMhvBr1OA>