Re: [ovirt-users] Error: Storage format V3 is not supported

Thank you! This worked, though I wish I documented the process better.... Becuase I am not sure what I did exactly that helped? # cat /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/metadata CLASS=Backup # changed DESCRIPTION=eport_storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 POOL_UUID= # I removed this REMOTE_PATH=<hostname>.<domain>.com:/mnt/export_ovirt/images # I changed this to what is listed ROLE=Regular SDUUID=4be3f6ac-7946-4e7b-9ca2-11731c8ba236 TYPE=NFS # changed VERSION=0 # changed from 3 to 0 ### I have tried this before with no succes, so it must be a combonation of other changes? _SHA_CKSUM=16dac1d1c915c4d30433f35dd668dd35f60dc22c # I changed this to what was found in the logs -Alex On Sun, Apr 3, 2016 at 2:31 AM, Vered Volansky <vered(a)redhat.com&gt; wrote: > I've reported the issue: > https://bugzilla.redhat.com/show_bug.cgi?id=1323462 > > A verified workaround is to change the metadata Version to 0. > > Checksum should be compromised by it, so follow > http://lists.ovirt.org/pipermail/users/2012-April/007149.html if you > have any issues with adjusting it. > > Please let me know how this worked out for you. > > Regards, > Vered > > On Thu, Mar 31, 2016 at 5:28 AM, Alex R <ar.digger(a)gmail.com&gt; wrote: > >> I am trying to import a domain that I have used as an export on a >> previous install. The previous install was no older then v3.5 and was >> built with the all-in-one-plugin. Before destroying that system I took a >> portable drive and made an export domain to export my VMs and templates. >> >> The new system is up to date an was built as a hosted engine. When I >> try to import the domain I get the following error: >> >> "Error while executing action: Cannot add Storage. Storage format V3 is >> not supported on the selected host version." >> >> I just need to recover the VMs. >> >> I connect the USB hard drive to the host and make an export directory >> just like I did on the old host. >> >> # ls -ld /mnt/export_ovirt >> drwxr-xr-x. 5 vdsm kvm 4096 Mar 6 11:27 /mnt/export_ovirt >> >> I have tried both doing an NFS mount >> # cat /etc/exports.d/ovirt.exports >> /home/engineha 127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash) >> /mnt/backup-vm/ 10.3.1.0/24(rw,anonuid=36,anongid=36,all_squash) >> 127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash) >> >> # cat >> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/metadata >> CLASS=Backup >> DESCRIPTION=eport_storage >> IOOPTIMEOUTSEC=10 >> LEASERETRIES=3 >> LEASETIMESEC=60 >> LOCKPOLICY= >> LOCKRENEWALINTERVALSEC=5 >> POOL_UUID=053926e4-e63d-450e-8aa7-6f1235b944c6 >> REMOTE_PATH=/mnt/export_ovirt/images >> ROLE=Regular >> SDUUID=4be3f6ac-7946-4e7b-9ca2-11731c8ba236 >> TYPE=LOCALFS >> VERSION=3 >> _SHA_CKSUM=2e6e203168bd84f3dc97c953b520ea8f78119bf0 >> >> # ls -l >> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf >> >> -rw-r--r--. 1 vdsm kvm 9021 Mar 6 11:50 >> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf >> >> Thanks, >> Alex >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users