[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#542441: marked as done (old LVM data is not erased)

Your message dated Mon, 10 Sep 2012 14:22:56 +0100
with message-id <504DE9B0.5070000@canonical.com>
and subject line old LVM data is not erased
has caused the Debian Bug report #542441,
regarding old LVM data is not erased
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
542441: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542441
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
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.

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: