I guess nobody has experienced such behaviour. I'm pretty sure that initial size of the disk was 100GB and after setting increase by 40 , I see size of 140GB - but my Linux and qemu-img see it as 180GB.
Anyone able to guide me through ? Maybe an update to 4.3.3 will solve it? Maybe I should open a bug, but what module is affecting me? Best Regards, Strahil NikolovOn Apr 6, 2019 04:54, Strahil Nikolov <[email protected]> wrote: > > Hi, > > I have just extended the disk of one of my openSuSE VMs and I have noticed > that despite the disk is only 140GiB (in UI), the VM sees it as 180GiB. > > I think that this should not happen at all. > > [root@ovirt1 ee8b1dce-c498-47ef-907f-8f1a6fe4e9be]# qemu-img info > c525f67d-92ac-4f36-a0ef-f8db501102fa > image: c525f67d-92ac-4f36-a0ef-f8db501102fa > file format: raw > virtual size: 180G (193273528320 bytes) > disk size: 71G > > Attaching some UI screen shots. > > Note: I have extended the disk via the UI by selecting 40GB (old value in UI > -> 100GB). > > Best Regards, > Strahil Nikolov >
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/4KYWIQKPTCOMF2227GOG7X4HPHUPIJA2/
