Red Hat Bugzilla – Bug 499967
anaconda wants to reformat/destroy too many lvm partitions
Last modified: 2009-06-01 18:53:21 EDT
Description of problem:
During an install of the F11 preview release (I tried both the live and the dvd versions), anaconda inexplicably decides it wants to reformat some partitions that I didn't ask it to.
Version-Release number of selected component (if applicable):
always reproducible for me.
Steps to Reproduce:
1. In anaconda storage section, select "create custom layout"
2. select a partition for / to be formatted, use a pre-existing /boot, ignoring all other pre-existing partitions.
dialog comes up warning about partitions selected to be formatted, destroying all data:
/dev/mapper/hothvg-f11lv ext4 /
It should only be reformatting f11lv, my slash partition, like this:
/dev/mapper/hothvg-f11lv ext4 /
I don't really know where the mimage volumes came from, but it shouldn't matter. I shouldn't have to figure that out during the install. The installer should only reformat things that I specifically chose to format. I can research where those "mimage" volumes came from after I have the install completed.
Created attachment 343223 [details]
vgdisplay -v output
Can you attach the files /tmp/storage.log, /tmp/program.log, and /tmp/anaconda.log?
Created attachment 343678 [details]
Created attachment 343679 [details]
Created attachment 343680 [details]
(In reply to comment #2)
> Can you attach the files /tmp/storage.log, /tmp/program.log, and
Can you generally describe your setup? I see that you have quite a few lvs, and then there are the _mimage_0 and _mlog lvs as well. Do you have some sort of mirroring or other advanced lvm configuration? The reason I am asking is that this does not happen with other lvm setups.
(In reply to comment #7)
> Can you generally describe your setup? I see that you have quite a few lvs, and
> then there are the _mimage_0 and _mlog lvs as well. Do you have some sort of
> mirroring or other advanced lvm configuration? The reason I am asking is that
> this does not happen with other lvm setups.
I have a bunch of logical volumes, some of them mirrored. I created most of them with "system-config-lvm". I did not do anything to create those "mimage" volumes, but I am leery about removing them until I understand where they came from. If your mirrorlog option is "disk", then those mlog volumes are created (see man lvconvert).
Recently I migrated some data from old disks to a new disk. In order to do that, I had to temporarily remove some of the "mlog" volumes by changing the mirrorlog type to "core". After I had moved the data onto the new disk, I changed them back to "disk". (I had to use the lvconvert command for this, since system-config-lvm has a fatal error if any of your mirrors are using a "core" mirror type, see related bug https://bugzilla.redhat.com/show_bug.cgi?id=494127).
Perhaps those mimage volumes are a by product of that recent migration? I'm not sure.
Regardless, I don't think anaconda should be doing anything with them. They have nothing to do with the install I am attempting.
Created attachment 343897 [details]
updates with proposed fix
Created attachment 343899 [details]
updates with proposed fix, this time against f11-pre
Please try the attached updates image and see if it solves this problem.
The same updates image is available here:
just in case you'd rather grab it from there.
(In reply to comment #10)
> Created an attachment (id=343899) [details]
> updates with proposed fix, this time against f11-pre
> Please try the attached updates image and see if it solves this problem.
Yup, that fixed it. The install was completed, and anaconda only listed my slash partition to be formatted.
This will be fixed in anaconda-18.104.22.168-1.