Partition table

luison

Renowned Member
Feb 22, 2010
158
5
83
Spain
elsurexiste.com
Hi. We are preparing a system hosted at OVH and perhaps due to not having experience with LVM we are having some issues with snapshots (vz) backups. We get errors like this:

command 'lvcreate --size 1024M --snapshot --name vzsnap-nsXXXXX.ovh.net-0 /dev/pve/LV' failed with exit code 5

OVH installations default a root ext3 partition and a large LVM partition for the VMs. Our doubts are with the fact of what would be the best partition structure for this considering that we want to have an additional (maybe more than one) ext partitions that we want to be shared across the different VMs via "bind" mounts.
With this in mind we are thinking about:

ext3_1/ root - (20Gb)
ext3_2/shared_data - (100Gb)
LVM_1 /var/lib/vz - (XXXGb) partition for virtual images
swap

Now... does this work well for the snapshots?
I've heard about the LVM requiring unallocated space of at least 1Gb for snapshots to work. Would this be completely disk unallocated or just spare unallocated within the LV group? Does it make sense to make it larger?

In any case I suppose we would have to just have unallocated space in the disk and then sort it once their installation is completed.

Thanks in advance for any advice or alternative recommended partition system.
 
Last edited:
Now... does this work well for the snapshots?
I've heard about the LVM requiring unallocated space of at least 1Gb for snapshots to work. Would this be completely disk unallocated or just spare unallocated within the LV group? Does it make sense to make it larger?

You need free space within the LV group. Default is 4GB.
 
Thanks for prompt response.

So this is... if I have a PVE group with say 386Gb the main LV logical volume should not be more than 382Gb with the rest remaining as unallocated space within the group, correct?

I'll try to suggest this to OVH as this must be causing some headaches to many. I am not sure how it can be archived with their control panel installations... I'll try by creating an additional logical partition within the group and the trying to get rid of it. Hope it works.