Centos 7.2.1511 clones entire volume as a single raw partition.

  • I have been using fog 1.2.0 for some time with Centos 6.5 - 6.8 which works fine. All my client machines have multiple (9 including boot, swap and tmp) ext3 partitions on a single disk. FOG creates those just fine with each partition being separate.

    Now I am stepping up to Centos 7.2 and the images are being captured as just two partitions. The boot is captured correctly as an xfs filesystem, but the entire volume managed portion of the disk is being captured as a single raw partition. I have tried with fog 1.2.0 running on my old Centos 6.7 and the latest fog 1.3.0 RC10 running on a new Centos 7.2 server. They both treat the volume managed portion of the disk a single giant raw partition. It wouldn’t bother me, but I am going to push this to 500 computers and it will take a significant amount of time given the size of the image it is creating.

    df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/mapper/centos-root 84G 8.3G 76G 10% /
    devtmpfs 16G 0 16G 0% /dev
    tmpfs 16G 80K 16G 1% /dev/shm
    tmpfs 16G 9.4M 16G 1% /run
    tmpfs 16G 0 16G 0% /sys/fs/cgroup
    /dev/sda1 497M 176M 321M 36% /boot
    /dev/mapper/centos-var 300G 877M 299G 1% /var
    /dev/mapper/centos-tmp 9.4G 33M 9.3G 1% /tmp
    /dev/mapper/centos-var_log 9.4G 43M 9.3G 1% /var/log
    /dev/mapper/centos-home 1.4T 402M 1.4T 1% /home
    /dev/mapper/centos-var_log_audit 9.4G 45M 9.3G 1% /var/log/audit
    tmpfs 3.2G 28K 3.2G 1% /run/user/1000
    tmpfs 3.2G 0 3.2G 0% /run/user/0

    more d1.partitions
    label: dos
    label-id: 0x00089853
    device: /dev/sda
    unit: sectors

    /dev/sda1 : start= 2048, size= 1024000, type=83, bootable
    /dev/sda2 : start= 1026048, size= 3903870976, type= 8e

    Is there something I am missing? I am not particularly stuck on volume management. That is the OS default, but it would be a pain to undo it now.

  • OK. Thanks. I guess I will just recreate my original image without LVM. I will probably get rid of the XFS while I am at it since they don’t shrink. BTW, 1.2.0 and 1.3.0 both treat the LVM partition the same.

    Again, thanks for the reply.

  • Senior Developer

    Yes, LVM is not a valid disk mode. FOG, particularly for 1.2.0 (and more likely for 1.3.0 as well) does not build LVM disks and pull partitions off the LVM. It reads “physical” disks. So /dev/sda1 = boot (it pulls that just fine but is small so hardly noticable), but /dev/sda2 = LVM which is not a volume type FOG recognizes.

Log in to reply