I ended up creating the VMs from scratch but I had only 3 so it wasn't that bad. I lost few days of work though. I'm sure the virtual disk was ok but oVirt could not recognize it correctly. I was able to import VMs only partially from connected storage domain but it did not import the disks. When I found the correct disk image in Glusterfs and uploaded it there was the size issue. The VM did not recognize the thin provision disk correctly. I also would like to know how to deal with such issues in case it happens again.
On Wed, Nov 14, 2018 at 4:07 PM Rob Epping <r.epp...@speakup.nl> wrote: > On Wed, 2018-11-07 at 16:05 +0000, Jarosław Prokopowski wrote: > > I was able to find the correct disk images in the glusterfs volume > > and > > uploaded one of them through the web interface and attached to > > corresponding imported virtual machine. > > The VM does not start completely. It complains now about disk size: > > Device /dev/sda2 has size of 22528 sectors which is smaller than > > corresponding PV size of 166746122 <16%20674%2061%2022> > > This is thin provision disk. > > We had a very similar issue where the disk image on gluster got > corrupted and ended-up being a similar size. > I'm interested in the fix for this. > -- > Met vriendelijke groet, > Rob Epping | NOC | Afdeling: +31 88 773 25 86 > > > +31 88 77 325 87 | www.speakup.nl > Institutenweg 6 7521 PK Enschede | Postbus 1330 7500 BH Enschede
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org 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/users@ovirt.org/message/ONYZ6SKANOMVIKHNHQ4YN6MEG6U3E3UJ/
