<div dir="ltr"><div><div><div><div>Federico,<br><br></div>You're a life savor.. Its was a permissions issues, somehow, the owner and group was assigned as root. I matched permission with the original data and it works! Cant believe I missed something so simple.<br>
</div></div>Thanks you!<br><br></div>Usman<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 4, 2013 at 11:07 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">Usman,<br>
the only thing that comes to my mind is something related to:<br>
<br>
<a href="http://gerrit.ovirt.org/13529" target="_blank">http://gerrit.ovirt.org/13529</a><br>
<br>
which means that in some way the restored volumes are either inaccessible<br>
(permissions?) or their metadata is corrupted (but it doesn't seem so).<br>
<br>
There is probably another Traceback in the logs that should give us more<br>
information.<br>
<br>
Could you post somewhere the entire vdsm log?<br>
<br>
Thanks.<br>
<div class="im">--<br>
Federico<br>
<br>
----- Original Message -----<br>
> From: "Usman Aslam" <<a href="mailto:usman@linkshift.com">usman@linkshift.com</a>><br>
</div><div class="im">> To: "Federico Simoncelli" <<a href="mailto:fsimonce@redhat.com">fsimonce@redhat.com</a>><br>
> Cc: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
> Sent: Friday, October 4, 2013 4:49:08 PM<br>
> Subject: Re: [Users] VM wont restart after some NFS snapshot restore.<br>
><br>
> Federico,<br>
><br>
> The files reside on this mount on the hypervisor<br>
> /rhev/data-center/mnt/<a href="http://xyz-02.tufts.edu" target="_blank">xyz-02.tufts.edu</a>:<br>
> _vol_tusk__vm_tusk__vm/fa3279ec-2912-45ac-b7bc-9fe89151ed99/images/79ccd989-3033-4e6a-80da-ba210c94225a<br>
><br>
> and are symlinked as described below<br>
><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<br>
> -> /rhev/data-center/mnt/<a href="http://xyz-02.tufts.edu" target="_blank">xyz-02.tufts.edu</a>:<br>
> _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<br>
> -> /rhev/data-center/mnt/<a href="http://xyz-02.tufts.edu" target="_blank">xyz-02.tufts.edu</a>:<br>
> _vol_tusk__vm_tusk__vm/fa3279ec-2912-45ac-b7bc-9fe89151ed99<br>
> lrwxrwxrwx 1 vdsm kvm 118 Oct 3 12:35 mastersd -><br>
> /rhev/data-center/mnt/<a href="http://xyz-02.tufts.edu" target="_blank">xyz-02.tufts.edu</a>:<br>
> _vol_tusk__vm_tusk__vm/fa3279ec-2912-45ac-b7bc-9fe89151ed99<br>
><br>
</div>> I did a diff and the contents of the the *Original *meta file (that works<br>
> and VM starts but have bad file system) and the *Backup *meta file (the<br>
> files being restored from nfs snapshot) *are exactly the same*.<br>
<div class="HOEnZb"><div class="h5">> Contents are listed blow. Also the files sizes for all six related files<br>
> are exactly the same.<br>
><br>
> [root@xyz-02 images]# cat<br>
> 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<br>
> 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<br>
><br>
> Any help would be greatly appreciated!<br>
><br>
> Thanks,<br>
> Usman<br>
><br>
><br>
> On Fri, Oct 4, 2013 at 9:50 AM, Federico Simoncelli<br>
> <<a href="mailto:fsimonce@redhat.com">fsimonce@redhat.com</a>>wrote:<br>
><br>
> > Hi Usman,<br>
> > can you paste somewhere the content of the meta files?<br>
> ><br>
> > $ cat 039a8482-c267-4051-b1e6-1c1dee49b3d7.meta<br>
> > 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>
> ><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<br>
> > VM<br>
> > > disk to a backup from a few days ago. So I powered the VM down, copied<br>
> > 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<br>
> > 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<br>
> > 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>
> > > _______________________________________________<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>
> ><br>
><br>
><br>
><br>
> --<br>
> Usman Aslam<br>
> <a href="tel:401.6.99.66.55" value="+14016996655">401.6.99.66.55</a><br>
> <a href="mailto:usman@linkshift.com">usman@linkshift.com</a><br>
><br>
</div></div></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>