Re: [Xen-users] XCP - corrupted VDI footer ?

[Joseph Hom <jhom@xxxxxxxxxxxxx>]

Is the VDI on some kind of network storage? 

I've had this happen due to the vhd semantics put onto lv for vdi. The 
semantics are sparse and the footer has to move everytime the disk "grows" in 
use. This can lead to the footer not being moved properly. 

I've had luck dd'ing out the lv to a flat file with the .vhd extension. After 
this you can import the vhd to winimage and have it make a copy of the disk. 
Winimage appears to ignore the bad footer and uses the backup. At this point 
you can make a new vhd with the data, and the dd the new vhd back to the lv.

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Kristoffer Egefelt
Sent: Thursday, December 29, 2011 4:45 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] XCP - corrupted VDI footer ?

Hi list,

I've seen corrupted footers on VDI's larger than 2TB, when physical machines 
crashed.

This time, the VDI is only 200GB, no physical machine has crashed and the 
virtual machine is functioning normally, but a SR rescan causes the following 
in the messages log (see below)

Any ideas how this happened, or what to do about it?

Thanks

Regards
Kristoffer


Dec 29 23:35:32 ad vhd-util: libvhd::vhd_read_footer_at: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 reading footer at 0x32197ffe00 failed: -22 Dec 29 23:35:32 ad vhd-util: 
libvhd::vhd_read: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 read of 512 returned 0, errno: -22 Dec 29 23:35:32 ad vhd-util: 
libvhd::vhd_read_short_footer: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 failed reading short footer: -22 Dec 29 23:35:32 ad vhd-util: 
libvhd::vhd_read_footer_at: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 reading footer at 0x32197ffe00 failed: -22 Dec 29 23:35:32 ad vhd-util: 
libvhd::vhd_read: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 read of 512 returned 0, errno: -22 Dec 29 23:35:32 ad vhd-util: 
libvhd::vhd_read_short_footer: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 failed reading short footer: -22 Dec 29 23:35:33 ad vhd-util: 
libvhd::vhd_read_footer_at: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 reading footer at 0x32197ffe00 failed: -22 Dec 29 23:35:33 ad vhd-util: 
libvhd::vhd_read: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 read of 512 returned 0, errno: -22 Dec 29 23:35:33 ad vhd-util: 
libvhd::vhd_read_short_footer: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 failed reading short footer: -22 Dec 29 23:35:33 ad vhd-util: 
libvhd::vhd_read_footer_at: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 reading footer at 0x32197ffe00 failed: -22 Dec 29 23:35:33 ad vhd-util: 
libvhd::vhd_read: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 read of 512 returned 0, errno: -22 Dec 29 23:35:33 ad vhd-util: 
libvhd::vhd_read_short_footer: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 failed reading short footer: -22 Dec 29 23:35:35 ad tapdisk[15898]: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 b: 102400, a: 3158, f: 987, n: 12968880 Dec 29 23:35:35 ad tapdisk[15898]: 
closed image 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f
 (0 users, state: 0x00000000, type: 4) Dec 29 23:35:38 ad tapdisk[15898]: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f
 version: tap 0x00010003, b: 102400, a: 0, f: 0, n: 8455 Dec 29 23:35:38 ad 
tapdisk[15898]: opened image 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f
 (1 users, state: 0x00000001, type: 4) Dec 29 23:35:38 ad tapdisk[15898]: 
/dev/VG_XenStorage-f60e4e9f-3b8a-0be7-07aa-59fdce05d4c3/VHD-35381293-f097-48e4-85cf-3382bc85446f:
 type:vhd(4) storage:lvm(3) _______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users