Wrong volume group size

SUSE Product Topics SLES Install-Boot
1

Hello,
I use autoyast to perform installation of my SLES12SP5 and I met an issue : during the pre-script phasis, I use a script to make partitioning. In this, I ask to have 2 volume group : 1 for /var/log, /tmp and /home with a size of 1024/768/256MiB so, 2GiB. Second volume group is for /root with the rest of disk.
For a 7GiB disk, I have this result :
fdisk -l
Disk /dev/sda: 7 GiB, 7516192768 bytes, 14680064 sectors
Disk model: Virtual disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00083158

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1060863 1058816 517M 83 Linux
/dev/sda2 1060864 2119679 1058816 517M 82 Linux swap / Solaris
/dev/sda3 2119680 8402943 6283264 3G 8e Linux LVM
/dev/sda4 8402944 14680063 6277120 3G 8e Linux LVM

Disk /dev/mapper/vg_root-lv_root: 3 GiB, 3200253952 bytes, 6250496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/vg_common-lv_home: 256 MiB, 268435456 bytes, 524288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/vg_common-lv_logs: 1 GiB, 1073741824 bytes, 2097152 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/vg_common-lv_tmp: 768 MiB, 805306368 bytes, 1572864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

For lsblk:
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
sda 8:0 0 7G 0 disk
??sda1 8:1 0 517M 0 part /boot
??sda2 8:2 0 517M 0 part [SWAP]
??sda3 8:3 0 3G 0 part
? ??vg_root-lv_root 254:0 0 3G 0 lvm /
??sda4 8:4 0 3G 0 part
??vg_common-lv_home 254:1 0 256M 0 lvm /home
??vg_common-lv_logs 254:2 0 1G 0 lvm /var/log
??vg_common-lv_tmp 254:3 0 768M 0 lvm /tmp

So, my first volume group is set to 3GiB instead of 2… why ? What am I missing ?

2

@Frederic Hi, so what does the script do, size, sectors, blocks etc? Perhaps a calculation error (GiB vs GB?)?

3

Here is the result of my script (the partitioning part) : https://drive.google.com/file/d/18pzaYC1eXG5d1-rGuGCQVKx8RBDYCMGA/view?usp=sharing

4

@Frederic Hi can you upload to https://susepaste.org/? Or just post if not too long in the thread with markup quotes eg three of these “`”.

5

@malcolmlewis Hi ! it’s done : https://susepaste.org/19817093

6

@Frederic Hi, strange indeed… I’m no autoyast user, but should size not have a suffix?

<size>1024M+256M+768M</size> or <size>2G</size> instead of <size>1024+256+768</size>

7

I tried with a <size>2G</size> but nothing changes

8

@Frederic Hi, well the only thing I can think of is moving the vg_root section to the last part of the file since it should process the rest of the disk (eg max)…

9

I tried to move the vg_root section after the vg_common, also change the <size>1024+256+768</size> by <size>2048M</size>, always the same result :frowning:

10

@Frederic Hi, are you in a position to open a Support Request? If so, that may be the best route, something is not right in autoyast land… :frowning:

11

Yes, I can do it.
Thanks for the help @malcolmlewis

12

maybe I was too tired yesterday evening but… with same VM, same autoyast xml file, I re-install the VM for saving some installation logs and it works this time !
I have my 2GiB vg_common and 4GiB vg_root…