Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I have a image with qcow2 format and created a flavor x-large with disk size 150GB. After somedays it starting to bloat and keepon increasing to 260GB now. My question is if we set the size of disk in flavour why the instance is consuming more storage.

I had a flavor x-large and details are below: qemu-img info /var/lib/nova/instances/b62da31b-83d1-4228 -92ee-75da2120fd58/disk image: /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58/disk file format: qcow2 virtual size: 150G (161061273600 bytes) disk size: 260G cluster_size: 65536 backing file: /var/lib/nova/instances/_base/c4cb69e2629d118506c456884778e0ffb68d 3bbf Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false Instance size on storage: du -sh /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58 260G /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58

openstack flavor show 3c5b20c1-1450-4460-a502-2984ef177767 +----------------------------+--------------------------------------+ | Field | Value | +----------------------------+--------------------------------------+ | OS-FLV-DISABLED:disabled | False | | OS-FLV-EXT-DATA:ephemeral | 0 | | disk | 40 | | id | 3c5b20c1-1450-4460-a502-2984ef177767 | | name | x-large | | os-flavor-access:is_public | True | | properties | | | ram | 16384 | | rxtx_factor | 1.0 | | swap | | | vcpus | 4 | +----------------------------+--------------------------------------+

If I login VM and check the size it is showing less than 150GB. I had same issue with some other images. My question 1. Is there is any issue with respect to images which are casing to consume more disk space or
2.Issue with any configuration. If there is any problem with configuration then rest of the images also consume storage.

I have a image with qcow2 format and created a flavor x-large with disk size 150GB. After somedays it starting to bloat and keepon increasing to 260GB now. My question is if we set the size of disk in flavour why the instance is consuming more storage.

I had a flavor x-large and details are below: qemu-img info /var/lib/nova/instances/b62da31b-83d1-4228 -92ee-75da2120fd58/disk image: /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58/disk file format: qcow2 virtual size: 150G (161061273600 bytes) disk size: 260G cluster_size: 65536 backing file: /var/lib/nova/instances/_base/c4cb69e2629d118506c456884778e0ffb68d 3bbf Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false Instance size on storage: du -sh /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58 260G /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58

openstack flavor show 3c5b20c1-1450-4460-a502-2984ef177767 +----------------------------+--------------------------------------+ | Field | Value | +----------------------------+--------------------------------------+ | OS-FLV-DISABLED:disabled | False | | OS-FLV-EXT-DATA:ephemeral | 0 | | disk | 40 | | id | 3c5b20c1-1450-4460-a502-2984ef177767 | | name | x-large | | os-flavor-access:is_public | True | | properties | | | ram | 16384 | | rxtx_factor | 1.0 | | swap | | | vcpus | 4 | +----------------------------+--------------------------------------+

If I login VM and check the size it is showing less than 150GB. I had same issue with some other images. My question 1. Is there is any issue with respect to images which are casing to consume more disk space or
2.Issue with any configuration. If there is any problem with configuration then rest of the images also consume storage.

I have a image created VM with qcow2 format 150GB disk flavor and created a flavor x-large with disk size 150GB. After somedays it starting to bloat and keepon increasing to 260GB now. started consuming more storage. My question is if we set the size of disk in flavour why the instance is consuming more storage.

I had a flavor x-large and details are below: qemu-img info /var/lib/nova/instances/b62da31b-83d1-4228 -92ee-75da2120fd58/disk image: /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58/disk file format: qcow2 virtual size: 150G (161061273600 bytes) disk size: 260G cluster_size: 65536 backing file: /var/lib/nova/instances/_base/c4cb69e2629d118506c456884778e0ffb68d 3bbf Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false Instance size on storage: du -sh /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58 260G /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58

openstack flavor show 3c5b20c1-1450-4460-a502-2984ef177767 +----------------------------+--------------------------------------+ | Field | Value | +----------------------------+--------------------------------------+ | OS-FLV-DISABLED:disabled | False | | OS-FLV-EXT-DATA:ephemeral | 0 | | disk | 40 | | id | 3c5b20c1-1450-4460-a502-2984ef177767 | | name | x-large | | os-flavor-access:is_public | True | | properties | | | ram | 16384 | | rxtx_factor | 1.0 | | swap | | | vcpus | 4 | +----------------------------+--------------------------------------+

If I login VM and check the size it is showing less than 150GB. I had same issue with some other images. My question 1. Is there is any issue with respect to images which are casing to consume more disk space or
2.Issue with any configuration. If there is any problem with configuration then rest of the images also consume storage.

click to hide/show revision 4
None

I have created VM Instance with 150GB disk flavor and it started consuming more storage. My question is if storage than what we set the size of disk in flavour why the instance is consuming more storage.flavour.

I had a flavor x-large and details are below: below:

qemu-img info /var/lib/nova/instances/b62da31b-83d1-4228                                                                              -92ee-75da2120fd58/disk
/var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58/disk
image: /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58/disk
file format: qcow2
virtual size: 150G (161061273600 bytes)
disk size: 260G
cluster_size: 65536
backing file: /var/lib/nova/instances/_base/c4cb69e2629d118506c456884778e0ffb68d                                                                              3bbf
/var/lib/nova/instances/_base/c4cb69e2629d118506c456884778e0ffb68d3bbf
Format specific information:
    compat: 1.1
    lazy refcounts: false
    refcount bits: 16
    corrupt: false

Instance size on storage: storage:

du -sh /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58                                                                   /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58
260G    /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58

/var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58 openstack flavor show 3c5b20c1-1450-4460-a502-2984ef177767 +----------------------------+--------------------------------------+ | Field | Value | +----------------------------+--------------------------------------+ | OS-FLV-DISABLED:disabled | False | | OS-FLV-EXT-DATA:ephemeral | 0 | | disk | 40 | | id | 3c5b20c1-1450-4460-a502-2984ef177767 | | name | x-large | | os-flavor-access:is_public | True | | properties | | | ram | 16384 | | rxtx_factor | 1.0 | | swap | | | vcpus | 4 | +----------------------------+--------------------------------------+

+----------------------------+--------------------------------------+

If I login VM and check the size it is showing less than 150GB. I had same issue with some other images. My question 1. questions:

  1. Is there is any issue with respect to images which are casing to consume more disk space or
    2.Issue
  2. Issue with any configuration. If there is any problem with configuration then rest of the images also consume storage.

    storage.

Instance with 150GB disk flavor started consuming more storage than what we set the size of disk in flavour.

I had a flavor x-large and details are below:

qemu-img info /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58/disk
image: /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58/disk
file format: qcow2
virtual size: 150G (161061273600 bytes)
disk size: 260G
cluster_size: 65536
backing file: /var/lib/nova/instances/_base/c4cb69e2629d118506c456884778e0ffb68d3bbf
Format specific information:
    compat: 1.1
    lazy refcounts: false
    refcount bits: 16
    corrupt: false

Instance size on storage:

du -sh /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58
260G    /var/lib/nova/instances/b62da31b-83d1-4228-92ee-75da2120fd58

openstack flavor show 3c5b20c1-1450-4460-a502-2984ef177767
+----------------------------+--------------------------------------+
| Field                      | Value                                |
+----------------------------+--------------------------------------+
| OS-FLV-DISABLED:disabled   | False                                |
| OS-FLV-EXT-DATA:ephemeral  | 0                                    |
| disk                       | 40                                   |
| id                         | 3c5b20c1-1450-4460-a502-2984ef177767 |
| name                       | x-large                              |
| os-flavor-access:is_public | True                                 |
| properties                 |                                      |
| ram                        | 16384                                |
| rxtx_factor                | 1.0                                  |
| swap                       |                                      |
| vcpus                      | 4                                    |
+----------------------------+--------------------------------------+

If I login VM and check the size it is showing less than 150GB. I had same issue with some other images. My questions:

  1. Is there is any issue with respect to images which are casing to consume more disk space or
  2. Issue with any configuration. If there is any problem with configuration then rest of the images also consume storage.

Since my env is Solaris, Below is the output of format and zpool list commands:

root@viweb-dr-test:/root# zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT rpool1 39.9G 15.7G 24.1G - 25% 39% 1.00x ONLINE -

Searching for disks...done

AVAILABLE DISK SELECTIONS: 0. c2t0d0 <virtio-block device-0000-40.00gb=""> /pci@0,0/pci1af4,2@4/blkdev@0,0 1. c3t0d0 <drive type="" unknown=""> /pci@0,0/pci1af4,2@5/blkdev@0,0