<div dir="ltr"><div><div><div><div><div>Federico,<br><br></div>The files reside on this mount on the hypervisor<br><span style="font-family:courier new,monospace"><span style="background-color:rgb(255,255,255)"><span style="color:rgb(53,28,117)">/rhev/data-center/mnt/xyz-02.tufts.edu:_vol_tusk__vm_tusk__vm/fa3279ec-2912-45ac-b7bc-9fe89151ed99/images/79ccd989-3033-4e6a-80da-ba210c94225a</span></span><br>
</span><br><span style="font-family:courier new,monospace"><span style="font-family:arial,helvetica,sans-serif">and are symlinked as described below</span><br><span style="color:rgb(53,28,117)"><br>[root@xyz-02 430cd986-6488-403b-8d46-29abbc3eba38]# pwd<br>
/rhev/data-center/430cd986-6488-403b-8d46-29abbc3eba38<br>[root@xyz-02 430cd986-6488-403b-8d46-29abbc3eba38]# ll<br>total 12<br>lrwxrwxrwx 1 vdsm kvm 120 Oct 3 12:35 ee2ae498-6e45-448d-8f91-0efca377dcf6 -> /rhev/data-center/mnt/xyz-02.tufts.edu:_vol_tusk__iso_tusk__iso/ee2ae498-6e45-448d-8f91-0efca377dcf6<br>
lrwxrwxrwx 1 vdsm kvm 118 Oct 3 12:35 fa3279ec-2912-45ac-b7bc-9fe89151ed99 -> /rhev/data-center/mnt/xyz-02.tufts.edu:_vol_tusk__vm_tusk__vm/fa3279ec-2912-45ac-b7bc-9fe89151ed99<br>lrwxrwxrwx 1 vdsm kvm 118 Oct 3 12:35 mastersd -> /rhev/data-center/mnt/xyz-02.tufts.edu:_vol_tusk__vm_tusk__vm/fa3279ec-2912-45ac-b7bc-9fe89151ed99<br>
</span></span><span style="color:rgb(53,28,117)"><br></span></div>I did a diff and the contents of the the <b>Original </b>meta file (that works and VM starts but have bad file system) and the <b>Backup </b>meta file (the files being restored from nfs snapshot) <b>are exactly the same</b>.<br>
</div>Contents are listed blow. Also the files sizes for all six related files are exactly the same.<br><br><span style="color:rgb(39,78,19)"><span style="font-family:courier new,monospace">[root@xyz-02 images]# cat 79ccd989-3033-4e6a-80da-ba210c94225a/039a8482-c267-4051-b1e6-1c1dee49b3d7.meta<br>
DOMAIN=fa3279ec-2912-45ac-b7bc-9fe89151ed99<br>VOLTYPE=SHARED<br>CTIME=1368457020<br>FORMAT=RAW<br>IMAGE=59b6a429-bd11-40c6-a218-78df840725c6<br>DISKTYPE=2<br>PUUID=00000000-0000-0000-0000-000000000000<br>LEGALITY=LEGAL<br>
MTIME=1368457020<br>POOL_UUID=<br>DESCRIPTION=Active VM<br>TYPE=SPARSE<br>SIZE=104857600<br>EOF<br>[root@tss-tusk-ovirt-02 images]# cat 79ccd989-3033-4e6a-80da-ba210c94225a/8d48505d-846d-49a7-8b50-d972ee051145.meta<br>DOMAIN=fa3279ec-2912-45ac-b7bc-9fe89151ed99<br>
CTIME=1370303194<br>FORMAT=COW<br>DISKTYPE=2<br>LEGALITY=LEGAL<br>SIZE=104857600<br>VOLTYPE=LEAF<br>DESCRIPTION=<br>IMAGE=79ccd989-3033-4e6a-80da-ba210c94225a<br>PUUID=039a8482-c267-4051-b1e6-1c1dee49b3d7<br>MTIME=1370303194<br>
POOL_UUID=<br>TYPE=SPARSE<br>EOF</span></span><br><br></div>Any help would be greatly appreciated!<br><br></div>Thanks,<br>Usman<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 4, 2013 at 9:50 AM, Federico Simoncelli <span dir="ltr"><<a href="mailto:fsimonce@redhat.com" target="_blank">fsimonce@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Usman,<br>
can you paste somewhere the content of the meta files?<br>
<br>
$ cat 039a8482-c267-4051-b1e6-1c1dee49b3d7.meta 8d48505d-846d-49a7-8b50-d972ee051145.meta<br>
<br>
could you also provide the absolute path to those files? (in the vdsm host)<br>
<br>
Thanks,<br>
--<br>
Federico<br>
<div><div class="h5"><br>
----- Original Message -----<br>
> From: "Usman Aslam" <<a href="mailto:usman@linkshift.com">usman@linkshift.com</a>><br>
> To: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
> Sent: Thursday, October 3, 2013 4:29:43 AM<br>
> Subject: [Users] VM wont restart after some NFS snapshot restore.<br>
><br>
> I have some VM's that live on NFS share. Basically, I had to revert the VM<br>
> disk to a backup from a few days ago. So I powered the VM down, copied over<br>
> the following files<br>
><br>
> 039a8482-c267-4051-b1e6-1c1dee49b3d7<br>
> 039a8482-c267-4051-b1e6-1c1dee49b3d7.lease<br>
> 039a8482-c267-4051-b1e6-1c1dee49b3d7.meta<br>
> 8d48505d-846d-49a7-8b50-d972ee051145<br>
> 8d48505d-846d-49a7-8b50-d972ee051145.lease<br>
> 8d48505d-846d-49a7-8b50-d972ee051145.meta<br>
><br>
> and now when I try to power the VM, it complains<br>
><br>
> 2013-Oct-02, 22:02:38<br>
> Failed to run VM zabbix-prod-01 (User: admin@internal).<br>
> 2013-Oct-02, 22:02:38<br>
> Failed to run VM zabbix-prod-01 on Host<br>
> <a href="http://tss-tusk-ovirt-01-ovirtmgmt.tusk.tufts.edu" target="_blank">tss-tusk-ovirt-01-ovirtmgmt.tusk.tufts.edu</a> .<br>
> 2013-Oct-02, 22:02:38<br>
> VM zabbix-prod-01 is down. Exit message: 'truesize'.<br>
><br>
> Any ideas on how I could resolve this? Perhaps a better way of approaching<br>
> the restore on a filesystem level?<br>
><br>
> I see the following the vsdm.log<br>
><br>
> Thread-7843::ERROR::2013-10-02<br>
> 22:02:37,548::vm::716::vm.Vm::(_startUnderlyingVm)<br>
> vmId=`8e8764ad-6b4c-48d8-9a19-fa5cf77208ef`::The vm start process failed<br>
> Traceback (most recent call last):<br>
> File "/usr/share/vdsm/vm.py", line 678, in _startUnderlyingVm<br>
> self._run()<br>
> File "/usr/share/vdsm/libvirtvm.py", line 1467, in _run<br>
> devices = self.buildConfDevices()<br>
> File "/usr/share/vdsm/vm.py", line 515, in buildConfDevices<br>
> self._normalizeVdsmImg(drv)<br>
> File "/usr/share/vdsm/vm.py", line 408, in _normalizeVdsmImg<br>
> drv['truesize'] = res['truesize']<br>
> KeyError: 'truesize'<br>
> Thread-7843::DEBUG::2013-10-02 22:02:37,553::vm::1065::vm.Vm::(setDownStatus)<br>
> vmId=`8e8764ad-6b4c-48d8-9a19-fa5cf77208ef`::Changed state to Down:<br>
> 'truesize'<br>
><br>
><br>
> Any help would be really nice, thanks!<br>
> --<br>
> Usman<br>
><br>
</div></div>> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
</blockquote></div><br><br clear="all"><br>-- <br>Usman Aslam<br>401.6.99.66.55<br><a href="mailto:usman@linkshift.com">usman@linkshift.com</a>
</div></div>