Debian Bug report logs - #542441
old LVM data is not erased

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Enrique Zanardi <ezanardi@atlantux.com>

To: submit@bugs.debian.org

Subject: old LVM data is not erased

Date: Wed, 19 Aug 2009 17:46:26 +0100

Package: partman-lvm
Version: 65
Severity: normal

While doing an automatic Lenny installation on a previously used disk,
I've found that debian-installer fails to erase the previous partition
data before using my partman-auto/expert_recipe . Therefore, it fails to
create the new VG and LVs, and stops there, displaying an error.

I think the problem is that the function device_remove_lvm , on
partman-lvm/lib/lvm-remove.sh , is not called from anywhere else in the
code on partman-lvm, partman-auto-lvm or partman-auto.

My preseed file contains the following partman related variables:

d-i partman-auto/disk string /dev/sda
d-i partman-auto/method string lvm
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-lvm/device_remove_lvm_span boolean true
d-i partman-auto/purge_lvm_from_device  boolean true
d-i partman-auto-lvm/new_vg_name string vg00
d-i partman-md/device_remove_md boolean true
d-i partman-lvm/confirm boolean true
d-i partman-basicmethods/method_only boolean false
d-i partman-auto/expert_recipe string           \
        boot-root-swap ::                       \
                128 512 256 ext3                \
                        $defaultignore{ }       \
                        $primary{ }             \
                        $bootable{ }            \
                        method{ format }        \
                        format{ }               \
                        use_filesystem{ }       \
                        filesystem{ ext3 }      \
                        mountpoint{ /boot }     \
                .                               \
                100 1000 -1 ext3                \
                        $defaultignore{ }       \
                        $primary{ }             \
                        method{ lvm }           \
                        vg_name{ vg00 }         \
                .                               \
                500 4000 -1 ext3                \
                        $lvmok{ }               \
                        in_vg{ vg00 }           \
                        $primary{ }             \
                        $bootable{ }            \
                        method{ format }        \
                        format{ }               \
                        use_filesystem{ }       \
                        filesystem{ ext3 }      \
                        mountpoint{ / }         \
                .                               \
                96 512 300% linux-swap          \
                        $lvmok{ }               \
                        in_vg{ vg00 }           \
                        method{ swap }          \
                        format{ }               \
                .

d-i partman-auto/choose_recipe select boot-root-swap
d-i partman/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true


-- 
Enrique Zanardi					ezanardi@atlantux.com

Message #10 received at 542441@bugs.debian.org (full text, mbox, reply):

From: Floris Bos <bos@je-eigen-domein.nl>

To: 542441@bugs.debian.org

Subject: #542441 Re: old LVM data is not erased

Date: Sun, 26 Dec 2010 04:01:08 +0100

Hi,

This old bug is still present in Squeeze, except that I have only seen it 
cause issues on systems with more than one disk.

If there is a LVM volume on the 2nd disk that has a group name that is the 
same Debian wants to use,  install fails with a red "Volume group name already 
in use"


To reproduce on a (virtual) system with 2 disks:

- install Debian.
- swap the disks cables, so that disk 1 becomes disk 2.
- try to install Debian again.


I think Debian should remove the labels from ALL disks if I specify "partman-
lvm/device_remove_lvm".
Or as an alternate solution pick a random volume group name by default, so 
there are not any conflicts.


-- 
Yours sincerely,

Floris Bos

Message #15 received at 542441@bugs.debian.org (full text, mbox, reply):

From: Marius Kotsbak <marius.kotsbak@gmail.com>

To: 542441@bugs.debian.org

Subject: Applies to debian-edu as well

Date: Sun, 05 Jun 2011 02:55:15 +0200

See 
http://user.skolelinux.org/~arntog/bug-screenshots/2011-06-04%2001.06.28.jpg

and bug report: http://bugs.skolelinux.org/show_bug.cgi?id=1466

--
Marius

Message #22 received at 542441-done@bugs.debian.org (full text, mbox, reply):

From: Dmitrijs Ledkovs <dmitrijs.ledkovs@canonical.com>

To: 542441-done@bugs.debian.org

Subject: old LVM data is not erased

Date: Mon, 10 Sep 2012 14:22:56 +0100

[Message part 1 (text/plain, inline)]

1) Steps partition as:
300 M - ext2 - /boot
the rest - lvm physical
\_ vg-group - debian
2) install, wipe partition table with fdisk o w
3) Partition again

Upon creating 'debian' VG the second time you will be notified that it
is already taken. You are thrown back into logical volume setup dialog,
but this time around it will show the "resurrected" LVMs. And you can
proceed to delete them or do as you please.

Potentially partman-lvm could rescan LVMs when entering this menu, or
clear LVM data when creating partitions.

But even the current behaviour, does not prevent to setup everything as
you want & complete the installation.

See bug 687160 with the patch that fixes failure to pre-seed in the
automatic partitioning.

-- 
Regards,
Dmitrijs.

[signature.asc (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.