[virt-tools-list] Virt-Manager did not allocate whole disk when creating the LVM volume
Michael
mine at michi.su
Thu Oct 9 08:05:50 UTC 2014
Quoting Cole Robinson <crobinso at redhat.com>:
> On 10/07/2014 02:09 PM, Michael wrote:
>> Hi,
>> some time ago I created a new LVM volume inside a LVM pool and did not
>> allocate the full volume size initially.
>>
>> Because of that Virt-Manager additionally created a snapshot for this
>> volume.
>>
>> How can I get rid of this snapshot? Can I just remove it with lvremove?
>> Or will there be some side effects?
>>
>> The volume data are:
>>
>> --- Logical volume ---
>> LV Path /dev/vg0/mine-mx0
>> LV Name mine-mx0
>> VG Name vg0
>> LV UUID Drydli-ecto-FGym-xwlM-8uMe-gDdp-xHskio
>> LV Write Access read/write
>> LV snapshot status active destination for mine-mx0_vorigin
>> LV Status available
>> # open 1
>> LV Size 150.00 GiB
>> Current LE 38400
>> COW-table size 98.83 GiB
>> COW-table LE 25300
>> Allocated to snapshot 53.19%
>> Snapshot chunk size 4.00 KiB
>> Segments 2
>> Allocation inherit
>> Read ahead sectors auto
>> - currently set to 256
>> Block device 252:15
>
> I believe if you request a not-fully-allocated lvm volume, then libvirt asks
> lvm to create a 'thin volume'. But that's the extent that I know, so
> maybe try
> googling 'lvm thin volume' for more info.
Thanks, I think that's going to lead me into the right direction.
Michael
More information about the virt-tools-list
mailing list