Federico,
The files reside on this mount on the hypervisor
/rhev/data-center/mnt/xyz-02.tufts.edu:_vol_tusk__vm_tusk__vm/fa3279ec-2912-45ac-b7bc-9fe89151ed99/images/79ccd989-3033-4e6a-80da-ba210c94225a
and are symlinked as described below
[root@xyz-02 430cd986-6488-403b-8d46-29abbc3eba38]# pwd
/rhev/data-center/430cd986-6488-403b-8d46-29abbc3eba38
[root@xyz-02 430cd986-6488-403b-8d46-29abbc3eba38]# ll
total 12
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
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
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
I did a diff and the contents of the the
Original meta file (that works and VM starts but have bad file system) and the
Backup meta file (the files being restored from nfs snapshot)
are exactly the same.
Contents are listed blow. Also the files sizes for all six related files are exactly the same.