Displaying 7 results from an estimated 7 matches for "789m".
Did you mean:
789
2018 May 22
1
Re: Create qcow2 v3 volumes via libvirt
...LV after testing it boots OK
directly from the image and it is in production again.
The VM itself reports ample space available:
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 789M 8.8M 780M 2% /run
/dev/mapper/RT--vg-root 51G 21G 28G 42% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/vda1 ...
2016 Jun 15
2
virt-sparsify changing the apparent-size of files
...ormat: qcow2
virtual size: 50G (53687091200 bytes)
disk size: 2.3G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: true
root@testingbox:/tmp/test # qemu-img info output.qcow2
image: output.qcow2
file format: qcow2
virtual size: 50G (53687091200 bytes)
disk size: 789M
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
Thanks!
2016 Jun 15
2
virt-sparsify changing the apparent-size of files
...ormat: qcow2
virtual size: 50G (53687091200 bytes)
disk size: 2.3G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: true
root@testingbox:/tmp/test # qemu-img info output.qcow2
image: output.qcow2
file format: qcow2
virtual size: 50G (53687091200 bytes)
disk size: 789M
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
Thanks!
2018 May 01
4
Re: Create qcow2 v3 volumes via libvirt
I have been using internal snapshots on production qcow2 images for a
couple of years, admittedly as infrequently as possible with one
exception and that exception has had multiple snapshots taken and
removed using virt-manager's GUI.
I was unaware of this:
> There are some technical downsides to
> internal snapshots IIUC, such as inability to free the space used by the
> internal
2016 Jun 17
1
Re: virt-sparsify changing the apparent-size of files
...> disk size: 2.3G
> cluster_size: 65536
> Format specific information:
> compat: 1.1
> lazy refcounts: true
> root@testingbox:/tmp/test # qemu-img info output.qcow2
> image: output.qcow2
> file format: qcow2
> virtual size: 50G (53687091200 bytes)
> disk size: 789M
> cluster_size: 65536
> Format specific information:
> compat: 1.1
> lazy refcounts: false
If I understand your question correctly, then everything is working as
it should.
For qcow2 files, the virtual size is not related to the "apparent"
size, as you can easily pro...
2016 Jun 17
1
Re: [libvirt-users] virt-sparsify changing the apparent-size of files
...> disk size: 2.3G
> cluster_size: 65536
> Format specific information:
> compat: 1.1
> lazy refcounts: true
> root@testingbox:/tmp/test # qemu-img info output.qcow2
> image: output.qcow2
> file format: qcow2
> virtual size: 50G (53687091200 bytes)
> disk size: 789M
> cluster_size: 65536
> Format specific information:
> compat: 1.1
> lazy refcounts: false
If I understand your question correctly, then everything is working as
it should.
For qcow2 files, the virtual size is not related to the "apparent"
size, as you can easily pro...
2016 Jun 22
0
Re: [libvirt-users] virt-sparsify changing the apparent-size of files
...65536
> > Format specific information:
> > compat: 1.1
> > lazy refcounts: true
> > root@testingbox:/tmp/test # qemu-img info output.qcow2
> > image: output.qcow2
> > file format: qcow2
> > virtual size: 50G (53687091200 bytes)
> > disk size: 789M
> > cluster_size: 65536
> > Format specific information:
> > compat: 1.1
> > lazy refcounts: false
>
> If I understand your question correctly, then everything is working as
> it should.
>
> For qcow2 files, the virtual size is not related to the &...