From: "Richard W.M. Jones" <rjones@redhat.com>
To: Milan Broz <gmazyland@gmail.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: [PATCH] wipefs: Add --force option
Date: Tue, 20 Nov 2012 15:41:06 +0000 [thread overview]
Message-ID: <20121120154106.GQ1444@rhmail.home.annexia.org> (raw)
In-Reply-To: <50AB9CB9.3040104@gmail.com>
On Tue, Nov 20, 2012 at 04:07:37PM +0100, Milan Broz wrote:
> On 11/20/2012 03:41 PM, Richard W.M. Jones wrote:
>
> > In fact the problem case is where you try to wipe a device which
> > contains a volume groups and a logical volume; note the LVs don't
> > contain filesystems, and nothing is mounted.
>
> Well there is a problem. While you can wipe part table, kernel will
> reload it and destroy all obsolete partitions.
> There should not be problem if it contains lvm, only if it contains
> active LVs mapped.
>
> If there are active device-mapper devices (either created by kpartx,
> lvm, crypt, ...) you will lost metadata and cannot remove them
> using standard tools, you are forced to do it with dmsetup later.
I guess this is not a problem for libguestfs (virt-format in this
case), since we throw away the appliance completely after each run.
We only care about what gets written to the disk.
But yes, I see your point.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
New in Fedora 11: Fedora Windows cross-compiler. Compile Windows
programs, test, and build Windows installers. Over 70 libraries supprt'd
http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw
prev parent reply other threads:[~2012-11-20 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 15:41 [PATCH] wipefs: Add --force option Richard W.M. Jones
2012-11-20 11:16 ` Karel Zak
2012-11-20 13:52 ` Karel Zak
2012-11-20 14:41 ` Richard W.M. Jones
2012-11-20 15:07 ` Milan Broz
2012-11-20 15:41 ` Richard W.M. Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121120154106.GQ1444@rhmail.home.annexia.org \
--to=rjones@redhat.com \
--cc=gmazyland@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).