FS#19448 - LVM (and maybe other device mapper stuff?) breaks AIF when there are hyphens in the name
Attached to Project:
Release Engineering
Opened by Lukas Grässlin (lukasg) - Thursday, 13 May 2010, 13:58 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 26 November 2012, 04:53 GMT
Opened by Lukas Grässlin (lukasg) - Thursday, 13 May 2010, 13:58 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 26 November 2012, 04:53 GMT
|
Details
I have a virtual machine with two disks.
Disk 1: 80 MB Boot partition and the rest on the second partition. Disk 2: completely clean, no partitions In the installer I choose /dev/sda2 and /dev/sdb as physical volumes. On this two I create and volumegroup and within this an logical volume. ext4 as filesystem. So, I'm finisched and confirming with "Done". It fails with a message, that maybe some devices could not be settled within 10s etc. and after that AIF exits with: "ERROR: process_filesystem needs a partition $1" On tty7 the last I can see is, that the installer created successfully the phsysical volumes. (pvdisplay confirms this.) But there are no volumegroup and no logial volume. |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Monday, 26 November 2012, 04:53 GMT
Reason for closing: Deferred
Monday, 26 November 2012, 04:53 GMT
Reason for closing: Deferred
Apparently AIF has problems with hypens in LV Names.
Just ran a quick test in a VM: 1 pv /dev/sda1, 1 vg named vg0, 1 lv named test-root
AIF exited with "Warning: Could not create all needed filesystems. Either the underlying blockdevices didn't became available in 10 iterations, or process_filesystem failed" and "ERROR: process_filesystem needs a partition as $1"
Problem seems to be related to the hyphen:
[root@archiso~]# ls /dev/mapper
control vg0-test--root
relevant line from /var/log/aif/aif.log:
[DEBUG FS ] /dev/mapper/vg0-test-root ext3 / no_opts no_label no_params ->Cannot do right now...
Evidently AIF fails to regognize that dm replaces - by --.
that's interesting. I did not know DM does that.
I couldn't find much info about this.
This seems to happen on devicefile names and in `dmsetup info` output, right?
Does it also happen in vgdisplay/pvdisplay/lvdisplay (can't check right now)? I guess not, because it only shows the names of separate things (i.e. just the vg, just the lv, never vgname-lvname)
About the other issue: aif does not support a Vg spanning multiple PV's. this is documented in the installation guide
I should use /dev/$vg/$lv rather then /dev/mapper/$vg-$lv, because all latter devicefiles have '-' replaced by '--' in $vg and $lv
When removing/editing a lv, it becomes impossible to edit/remove previously created lv.
https://github.com/Dieterbe/aif/commit/ccb45e816580091028bfab11516991542e62e2ce
however, needs testing. this will be in a new build @ http://releng.archlinux.org/isos/ tomorrow