virtual machine actual size is not right
Dear all, I would like to know the actual size that the virtual machine is used. I found that there is a field to show "actual size". But the number is not right. I entered the server and type df -h. The storage size of the server is about 30GB but the actual size field shows 60 GB. Regards Terry
Hi just small clarification I entered the server and type df -h. - do you meant you run this command on host which is running mentioned VM? On Thu, Mar 22, 2018 at 4:47 AM, Terry hey <recreationh@gmail.com> wrote:
Dear all,
I would like to know the actual size that the virtual machine is used. I found that there is a field to show "actual size". But the number is not right.
I entered the server and type df -h. The storage size of the server is about 30GB but the actual size field shows 60 GB.
Regards Terry
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- PAVOL BRILLA RHV QUALITY ENGINEER, CLOUD Red Hat Czech Republic, Brno <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
Hi For such big difference between size outside of VM and inside, it looks more that disk is not fully partioned. df is providing you information only about mounted filesystems. Could you try to run inside VM should match all local disks, and you should see size of disk : # parted -l /dev/[sv]d[a-z] | grep ^Disk ( Output of 1 of my VMs ): # parted -l /dev/[sv]d[a-z] | grep ^Disk Disk /dev/sda: 26.8GB Disk Flags: Disk /dev/mapper/rootvg-lv_tmp: 2147MB Disk Flags: Disk /dev/mapper/rootvg-lv_home: 210MB Disk Flags: Disk /dev/mapper/rootvg-lv_swap: 2147MB Disk Flags: Disk /dev/mapper/rootvg-lv_root: 21.8GB So I see that VM has 26.8GB big disk. On Thu, Mar 22, 2018 at 5:56 PM, Terry hey <recreationh@gmail.com> wrote:
Hello~ i type this command on the running vm, not the hypervisor ( ovirt node).
-- PAVOL BRILLA RHV QUALITY ENGINEER, CLOUD Red Hat Czech Republic, Brno <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
Hello, thank you for helping me. On the storage domain size: Alias: host1 Disk: 1 Template: Blank Virtual Size: 30 GB Actual Size: 13 GB Creation Date: Jan 29,2018 11:22:54 AM On the server size: # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg01-root 10G 7.2G 2.9G 72% / devtmpfs 1.9G 0 1.9G 0% /dev tmpfs 1.9G 4.0K 1.9G 1% /dev/shm tmpfs 1.9G 17M 1.9G 1% /run tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/sda1 1014M 188M 827M 19% /boot /dev/mapper/vg01-var 15G 996M 15G 7% /var XXX.XXX.XXX.XXX:/nfs_share 249G 96G 141G 41% /mnt/nfs_share tmpfs 379M 0 379M 0% /run/user/0 # parted -l /dev/[sv]d[a-z] | grep ^Disk Disk /dev/sda: 32.2GB Disk Flags: Disk /dev/mapper/vg01-var: 16.1GB Disk Flags: Disk /dev/mapper/vg01-swap: 2147MB Disk Flags: Disk /dev/mapper/vg01-root: 10.7GB Disk Flags: # It still not the same. Also, do you know the upper limitation for thin provision? For example, if i allocated 30 GB to the hosts, what is the upper limitation that the host can use? Regards, Terry 2018-03-23 18:45 GMT+08:00 Pavol Brilla <pbrilla@redhat.com>:
Hi
For such big difference between size outside of VM and inside, it looks more that disk is not fully partioned. df is providing you information only about mounted filesystems. Could you try to run inside VM should match all local disks, and you should see size of disk : # parted -l /dev/[sv]d[a-z] | grep ^Disk
( Output of 1 of my VMs ): # parted -l /dev/[sv]d[a-z] | grep ^Disk Disk /dev/sda: 26.8GB Disk Flags: Disk /dev/mapper/rootvg-lv_tmp: 2147MB Disk Flags: Disk /dev/mapper/rootvg-lv_home: 210MB Disk Flags: Disk /dev/mapper/rootvg-lv_swap: 2147MB Disk Flags: Disk /dev/mapper/rootvg-lv_root: 21.8GB
So I see that VM has 26.8GB big disk.
On Thu, Mar 22, 2018 at 5:56 PM, Terry hey <recreationh@gmail.com> wrote:
Hello~ i type this command on the running vm, not the hypervisor ( ovirt node).
--
PAVOL BRILLA
RHV QUALITY ENGINEER, CLOUD
Red Hat Czech Republic, Brno <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
Hi just small note why size of disk differs between ovirt and system: 30G in ovirt = 30*1024*1024*1024 bytes = 32212254720 bytes = 32.2GB which you see in parted output I dont know that much about storage to help with it and I can only cite from oVirt webpages[1]: Thin Provision allocates 1 GB at the time the virtual disk is created and sets a maximum limit on the size to which the disk can grow. The virtual size of the disk is the maximum limit; the actual size of the disk is the space that has been allocated so far. Thinly provisioned disks are faster to create than preallocated disks and allow for storage over-commitment. Thinly provisioned virtual disks are recommended for desktops. [1] https://www.ovirt.org/documentation/admin-guide/chap-Virtual_Machine_Disks/ On Tue, Mar 27, 2018 at 9:02 AM, Terry hey <recreationh@gmail.com> wrote:
Hello, thank you for helping me.
On the storage domain size: Alias: host1 Disk: 1 Template: Blank Virtual Size: 30 GB Actual Size: 13 GB Creation Date: Jan 29,2018 11:22:54 AM
On the server size: # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg01-root 10G 7.2G 2.9G 72% / devtmpfs 1.9G 0 1.9G 0% /dev tmpfs 1.9G 4.0K 1.9G 1% /dev/shm tmpfs 1.9G 17M 1.9G 1% /run tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/sda1 1014M 188M 827M 19% /boot /dev/mapper/vg01-var 15G 996M 15G 7% /var XXX.XXX.XXX.XXX:/nfs_share 249G 96G 141G 41% /mnt/nfs_share tmpfs 379M 0 379M 0% /run/user/0
# parted -l /dev/[sv]d[a-z] | grep ^Disk Disk /dev/sda: 32.2GB Disk Flags: Disk /dev/mapper/vg01-var: 16.1GB Disk Flags: Disk /dev/mapper/vg01-swap: 2147MB Disk Flags: Disk /dev/mapper/vg01-root: 10.7GB Disk Flags: #
It still not the same. Also, do you know the upper limitation for thin provision? For example, if i allocated 30 GB to the hosts, what is the upper limitation that the host can use?
Regards, Terry
2018-03-23 18:45 GMT+08:00 Pavol Brilla <pbrilla@redhat.com>:
Hi
For such big difference between size outside of VM and inside, it looks more that disk is not fully partioned. df is providing you information only about mounted filesystems. Could you try to run inside VM should match all local disks, and you should see size of disk : # parted -l /dev/[sv]d[a-z] | grep ^Disk
( Output of 1 of my VMs ): # parted -l /dev/[sv]d[a-z] | grep ^Disk Disk /dev/sda: 26.8GB Disk Flags: Disk /dev/mapper/rootvg-lv_tmp: 2147MB Disk Flags: Disk /dev/mapper/rootvg-lv_home: 210MB Disk Flags: Disk /dev/mapper/rootvg-lv_swap: 2147MB Disk Flags: Disk /dev/mapper/rootvg-lv_root: 21.8GB
So I see that VM has 26.8GB big disk.
On Thu, Mar 22, 2018 at 5:56 PM, Terry hey <recreationh@gmail.com> wrote:
Hello~ i type this command on the running vm, not the hypervisor ( ovirt node).
--
PAVOL BRILLA
RHV QUALITY ENGINEER, CLOUD
Red Hat Czech Republic, Brno <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
-- PAVOL BRILLA RHV QUALITY ENGINEER, CLOUD Red Hat Czech Republic, Brno <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
participants (2)
-
Pavol Brilla -
Terry hey