Displaying 3 results from an estimated 3 matches for "325g".
Did you mean:
325
2014 Apr 10
2
Help with understanding and solving snapshot problem
...p1-host1.qcow2
file format: qcow2
virtual size: 24G (25769803776 bytes)
disk size: 3.5G
cluster_size: 65536
[root@cocoa libvirt]# qemu-img info /var/lib/libvirt/snap1-host1-db.qcow2
image: /var/lib/libvirt/snap1-host1-db.qcow2
file format: qcow2
virtual size: 1.6T (1800279089664 bytes)
disk size: 325G
cluster_size: 65536
What have I done wrong and how can I correct this so I can discard the existing snapshot and have a snapshot of the system excluding the second disk (and optionally which I can re-take at intervals and discard old ones)?
Many thanks,
rolf.
2014 Apr 10
0
Re: Help with understanding and solving snapshot problem
...it more obvious what the
domain was using at the time you took the snapshot?
>
> [root@cocoa libvirt]# qemu-img info /var/lib/libvirt/snap1-host1-db.qcow2
> image: /var/lib/libvirt/snap1-host1-db.qcow2
> file format: qcow2
> virtual size: 1.6T (1800279089664 bytes)
> disk size: 325G
> cluster_size: 65536
>
> What have I done wrong and how can I correct this so I can discard the existing snapshot and have a snapshot of the system excluding the second disk (and optionally which I can re-take at intervals and discard old ones)?
I don't quite have a full picture of...
2014 Apr 10
2
Re: Help with understanding and solving snapshot problem
...shot>
Not completely sure what to derive from that output?
>> [root@cocoa libvirt]# qemu-img info /var/lib/libvirt/snap1-host1-db.qcow2
>> image: /var/lib/libvirt/snap1-host1-db.qcow2
>> file format: qcow2
>> virtual size: 1.6T (1800279089664 bytes)
>> disk size: 325G
>> cluster_size: 65536
>>
>
> I don't quite have a full picture of how you got into the situation. If
> you are trying to just get rid of the snapshot, you could always try
> 'virsh snapshot-delete --metadata host1 snap1-host1', to make libvirt
> forget abo...