Creating an AMI image with lvm2 defined physical volumes, logical volumes, volume groups, and filesystems

Question

I created an AMI image that used lvm2 to create physical volumes, logical volumes, volume groups, and filesystems.   I expected when I launched a new instance from the AMI, the lvm defined physical volumes, volume groups, and filesystems would transfer.    However, only the non-lvm defined filesystems were created in the new EC2 instance.    When creating/launching an image, are there additional steps to follow to preserve the lvm defined data?   Thanks

Accepted Answer

Is the problem that any LVM commands like `pvdisplay` or `vgs` etc. always come back with an error of the form `Devices file sys_wwid nvme.1d0f-[big_long_random_string] PVID [shorter_random_string] last seen on /dev/sdb not found.` ? I hope it is, because that's the behaviour I've managed to replicate :-)

Not sure whether to call this a fix, or a workaround, or a hack, but anyway what you need to do ensure **use_devicesfile = 0** is present in **/etc/lvm/lvm.conf** on the instance from which the AMI is created, and then create a fresh AMI with this entry in place.
```
sed -i 's/# use_devicesfile = 0/use_devicesfile = 0/' /etc/lvm/lvm.conf
```
See comment #8 of https://bugzilla.redhat.com/show_bug.cgi?id=2072201

I tested with an entry in **/etc/fstab** for an filesystem on an LVM volume, and it mounts the first time a new EC2 is booted from the AMI, with no manual intervention required.

Creating an AMI image with lvm2 defined physical volumes, logical volumes, volume groups, and filesystems

Contenido relevante