Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

disk size of qcow2-image is unexpectable

Hi all A strange thing happended in my compute-node. I have compute-nodes with NFS mounted for Nova instances.

df

Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda2 96121612 4416432 86822392 5% / udev 132033912 4 132033908 1% /dev tmpfs 52817272 364 52816908 1% /run none 5120 0 5120 0% /run/lock none 132043172 0 132043172 0% /run/shm cgroup 132043172 0 132043172 0% /sys/fs/cgroup 192.168.100.242:/TEST_nova_nfs 419430400 192433600 226996800 46% /opt/openstack/instances

I create VM with snapshot image which format is qcow2. The OS type of Image is Window 7 pro. And I found that the disk size of VM is strange because the max size of disk is 100GB but current size of disk is 345GB.

Please see below : root@TEST01H:/opt/openstack/instances/3116cff3-0d1f-4f5b-ab7d-06c9baed6a9a# ls -alh total 346G drwxrwxr-x 2 novasvc novasvc 4.0K Feb 25 23:16 . drwxr-xr-x 199 novasvc novasvc 24K Feb 27 10:50 .. -rw-rw---- 1 libvirt-qemu kvm 0 Feb 23 19:49 console.log -rw-r--r-- 1 libvirt-qemu kvm 722G Mar 2 10:08 disk -rw-r--r-- 1 novasvc novasvc 80 Jan 28 15:25 disk.info -rw-rw-r-- 1 novasvc novasvc 1.8K Feb 23 19:43 libvirt.xml

qemu-img info disk

image: disk file format: qcow2 virtual size: 100G (107374182400 bytes) disk size: 345G cluster_size: 65536 backing file: /opt/openstack/instances/_base/db74b6aff4e2f5590b121431afa425a2dba57ad5

is this possible? and I cannot understand how is this thing happended.

Thanks in advance.

disk size of qcow2-image is unexpectable

Hi all A strange thing happended in my compute-node. compute-node.
I have compute-nodes with NFS mounted for Nova instances.

# df


Filesystem 1K-blocks Used Available Use% Mounted on on
/dev/sda2 96121612 4416432 86822392 5% / /
udev 132033912 4 132033908 1% /dev /dev
tmpfs 52817272 364 52816908 1% /run /run
none 5120 0 5120 0% /run/lock /run/lock
none 132043172 0 132043172 0% /run/shm /run/shm
cgroup 132043172 0 132043172 0% /sys/fs/cgroup /sys/fs/cgroup
192.168.100.242:/TEST_nova_nfs 419430400 192433600 226996800 46% /opt/openstack/instances

I create VM with snapshot image which format is qcow2. qcow2.
The OS type of Image is Window 7 pro. pro.
And I found that the disk size of VM is strange because the max size of disk is 100GB but current size of disk is 345GB.

Please see below :
root@TEST01H:/opt/openstack/instances/3116cff3-0d1f-4f5b-ab7d-06c9baed6a9a# ls -alh -alh
total 346G 346G
drwxrwxr-x 2 novasvc novasvc 4.0K Feb 25 23:16 . .
drwxr-xr-x 199 novasvc novasvc 24K Feb 27 10:50 .. ..
-rw-rw---- 1 libvirt-qemu kvm 0 Feb 23 19:49 console.log console.log
-rw-r--r-- 1 libvirt-qemu kvm 722G Mar 2 10:08 disk disk
-rw-r--r-- 1 novasvc novasvc 80 Jan 28 15:25 disk.info disk.info
-rw-rw-r-- 1 novasvc novasvc 1.8K Feb 23 19:43 libvirt.xml

# qemu-img info disk *
image:
disk

image: disk
file format: qcow2 qcow2
*
virtual size: 100G (107374182400 bytes) bytes)
disk size: 345G

cluster_size: 65536 65536
backing file: /opt/openstack/instances/_base/db74b6aff4e2f5590b121431afa425a2dba57ad5

is this possible? and I cannot understand how is this thing happended.

Thanks in advance.

disk size of qcow2-image is unexpectable

Hi all all.
A strange thing happended in my compute-node.
I have compute-nodes with NFS mounted for Nova instances.

# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 96121612 4416432 86822392 5% /
udev 132033912 4 132033908 1% /dev
tmpfs 52817272 364 52816908 1% /run
none 5120 0 5120 0% /run/lock
none 132043172 0 132043172 0% /run/shm
cgroup 132043172 0 132043172 0% /sys/fs/cgroup
192.168.100.242:/TEST_nova_nfs 419430400 192433600 226996800 46% /opt/openstack/instances

I create VM with from vm snapshot image which format is qcow2.
The OS type of Image is Window 7 pro.
And I found that the disk size of VM is strange because the max size of disk is 100GB but current size of disk is 345GB.

Please see below :
root@TEST01H:/opt/openstack/instances/3116cff3-0d1f-4f5b-ab7d-06c9baed6a9a# ls -alh
total 346G
drwxrwxr-x 2 novasvc novasvc 4.0K Feb 25 23:16 .
drwxr-xr-x 199 novasvc novasvc 24K Feb 27 10:50 ..
-rw-rw---- 1 libvirt-qemu kvm 0 Feb 23 19:49 console.log
-rw-r--r-- 1 libvirt-qemu kvm 722G Mar 2 10:08 disk
-rw-r--r-- 1 novasvc novasvc 80 Jan 28 15:25 disk.info
-rw-rw-r-- 1 novasvc novasvc 1.8K Feb 23 19:43 libvirt.xml

# qemu-img info disk *
image: disk
file format: qcow2
*
virtual size: 100G (107374182400 bytes)
disk size: 345G

cluster_size: 65536
backing file: /opt/openstack/instances/_base/db74b6aff4e2f5590b121431afa425a2dba57ad5

is this possible? and I cannot understand how is this thing happended.

Thanks in advance.

disk size of qcow2-image is unexpectable

Hi all.
A strange thing happended in my compute-node.
I have compute-nodes with NFS mounted for Nova instances.

# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 96121612 4416432 86822392 5% /
udev 132033912 4 132033908 1% /dev
tmpfs 52817272 364 52816908 1% /run
none 5120 0 5120 0% /run/lock
none 132043172 0 132043172 0% /run/shm
cgroup 132043172 0 132043172 0% /sys/fs/cgroup
192.168.100.242:/TEST_nova_nfs 419430400 192433600 226996800 46% /opt/openstack/instances

I create VM from vm snapshot image which format is qcow2.
The OS type of Image is Window 7 pro.
And I found that the disk size of VM is strange because the max size of disk is 100GB but current size of disk is 345GB.

Please see below :
root@TEST01H:/opt/openstack/instances/3116cff3-0d1f-4f5b-ab7d-06c9baed6a9a# ls -alh
total 346G
drwxrwxr-x 2 novasvc novasvc 4.0K Feb 25 23:16 .
drwxr-xr-x 199 novasvc novasvc 24K Feb 27 10:50 ..
-rw-rw---- 1 libvirt-qemu kvm 0 Feb 23 19:49 console.log
-rw-r--r-- 1 libvirt-qemu kvm 722G Mar 2 10:08 disk
-rw-r--r-- 1 novasvc novasvc 80 Jan 28 15:25 disk.info
-rw-rw-r-- 1 novasvc novasvc 1.8K Feb 23 19:43 libvirt.xml

# qemu-img info disk *
image: disk
file format: qcow2
*
virtual size: 100G (107374182400 bytes)
disk size: 345G

cluster_size: 65536
backing file: /opt/openstack/instances/_base/db74b6aff4e2f5590b121431afa425a2dba57ad5

is this possible? and I cannot understand how is this thing happended.

Thanks in advance.

disk size of qcow2-image is unexpectable

Hi all.
A strange thing happended in my compute-node.
I have compute-nodes with NFS mounted for Nova instances.

# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 96121612 4416432 86822392 5% /
udev 132033912 4 132033908 1% /dev
tmpfs 52817272 364 52816908 1% /run
none 5120 0 5120 0% /run/lock
none 132043172 0 132043172 0% /run/shm
cgroup 132043172 0 132043172 0% /sys/fs/cgroup
192.168.100.242:/TEST_nova_nfs 419430400 192433600 226996800 46% /opt/openstack/instances

I create VM from vm snapshot image which format is qcow2.
The OS type of Image is Window 7 pro.
And I found that the disk size of VM is strange because the max size of disk is 100GB but current size of disk is 345GB.

Please see below :
root@TEST01H:/opt/openstack/instances/3116cff3-0d1f-4f5b-ab7d-06c9baed6a9a# ls -alh
total 346G
drwxrwxr-x 2 novasvc novasvc 4.0K Feb 25 23:16 .
drwxr-xr-x 199 novasvc novasvc 24K Feb 27 10:50 ..
-rw-rw---- 1 libvirt-qemu kvm 0 Feb 23 19:49 console.log
-rw-r--r-- 1 libvirt-qemu kvm 722G Mar 2 10:08 disk
-rw-r--r-- 1 novasvc novasvc 80 Jan 28 15:25 disk.info
-rw-rw-r-- 1 novasvc novasvc 1.8K Feb 23 19:43 libvirt.xml

# qemu-img info disk *
image: disk
file format: qcow2
*
virtual size: 100G (107374182400 bytes)
disk size: 345G

cluster_size: 65536
backing file: /opt/openstack/instances/_base/db74b6aff4e2f5590b121431afa425a2dba57ad5

is this possible? and I cannot understand how is this thing happended.

Thanks in advance.