I looked around but could not find any info on how to expand a libvirt managed
LVM storage pool. I do not see any virsh command to do it
but I was successful using the vgexpand command to add some more storage once I
destroyed the pools and then restarted it.
I'd like to verify that this is the proper way to grow the storage in a libvirt
LVM storage pool. And this brings up a second
question, I did this without any VM running so I'd like to know what the impact
of destroying a running pool is on running VMs.
Does taking the pool off-line cause any issues with running VMs or is the only
affect that the pool is unavailable for management by libvirt?
These are the commands that I ran to create my pool and expand it after a
kickstart of the server:
pvcreate -ff -y /dev/mapper/mpath?
virsh pool-define-as --name GuestVols --type logical --source-dev
/dev/mapper/mpatha --target /dev/GuestVols
virsh pool-build GuestVols
virsh pool-start GuestVols
virsh pool-autostart GuestVols
virsh pool-destroy --pool GuestVols
vgextend GuestVols /dev/mapper/mpath{b..d}
vgdisplay GuestVols
virsh pool-start --pool GuestVols
virsh pool-info --pool GuestVols
Is this the best way to create a managed pool across 4 LUNs? And to potentially
expand the storage group in the future if more storage is needed?
--jim
_______________________________________________
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
