|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-API] problem accessing lvmoiscsi vhd : libvhd::vhd_validate_footer: invalid footer cookie:
Hi again Julian, This sounds possibly like a different sort of failure to the hotfix issue.I think I've had the failure of the hotfix a month ago after a snapshot, and I had recovered all the data by mounting the parent VHD. I was hoping it was a similar problem in order to have a similar solution...Can you run an sr-scan on that SR and check the output. See if you get a failure and entries in the /var/log/SMlog file that indicate vhd-util scan was unable to read VHD headers.Yes the SR scan does not work and it slowly fills up my logs every 30 seconds. May 16 18:31:58 srvxen1 xapi: [error|srvxen1|1104715 unix-RPC|SR.scan R:6abf3b5a9bc3|xapi] Caught error scanning SR (xcp_sda1_san2): SR_BACKEND_FAILURE_46: [ ; The VDI is not available [opterr=Error scanning VDI 587aa01a-878e-42b6-a272-fc627c407340]; ]. Using vhd-util, it gives me the following error : actually on the VHD I'm the most in the need for, the error message is more hopefull : [root@srvxen1 ~]# vhd-util check -n /dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-fac1dc4a-e56b-48b7-9327-c68b3e10fbe4 primary footer invalid: invalid cookie/dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-fac1dc4a-e56b-48b7-9327-c68b3e10fbe4 appears invalid; dumping metadata
VHD Footer Summary:
-------------------
Cookie : conectix
Features : (0x00000002) <RESV>
File format version : Major: 1, Minor: 0
Data offset : 512
Timestamp : Fri May 13 04:47:29 2011
Creator Application : 'tap'
Creator version : Major: 1, Minor: 3
Creator OS : Unknown!
Original disk size : 8192 MB (8589934592 Bytes)
Current disk size : 25600 MB (26843545600 Bytes)
Geometry : Cyl: 52012, Hds: 16, Sctrs: 63
: = 25599 MB (26843185152 Bytes)
Disk type : Differencing hard disk
Checksum : 0xffffefb5|0xffffefb5 (Good!)
UUID : 931980f2-d776-420b-9888-e54cf4aa43f8
Saved state : No
Hidden : 0
VHD Header Summary:
-------------------
Cookie : cxsparse
Data offset (unusd) : 18446744073709
Table offset : 1536
Header version : 0x00010000
Max BAT size : 1048576
Block size : 2097152 (2 MB)
Parent name :
VG_XenStorage--f489b51d--7b20--62a7--d9f3--829a149cfb2e-VHD--58b3d50e--3772--4fce--a35e--2eff31e5a2ab
Parent UUID : 9bf43490-39e8-4ed6-b432-b4f8e9e277e6
Parent timestamp : Fri May 13 04:47:29 2011
Checksum : 0xffffc60f|0xffffc60f (Good!)
VHD Parent Locators:
--------------------
locator: : 0
code : PLAT_CODE_MACX
data_space : 512
data_length : 110
data_offset : 4327424
failed to read parent name
locator: : 1
code : PLAT_CODE_W2KU
data_space : 512
data_length : 206
data_offset : 4327936
decoded name :
locator: : 2
code : PLAT_CODE_W2RU
data_space : 512
data_length : 206
data_offset : 4328448
decoded name :
failed to get batmap header
I guess here the main issue is the "failed to read parent name"...
Thanks for the help
Denis
[root@srvxen1 ~]# vhd-util check -n /dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-847c6b12-de04-446d-9551-6b8ebc4e01d8 primary footer invalid: invalid cookie /dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-847c6b12-de04-446d-9551-6b8ebc4e01d8 appears invalid; dumping metadata Failed to open /dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-847c6b12-de04-446d-9551-6b8ebc4e01d8: -22 /dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-847c6b12-de04-446d-9551-6b8ebc4e01d8 appears invalid; dumping headers VHD Footer Summary: ------------------- Cookie : Features : (0x00000000) File format version : Major: 0, Minor: 0 Data offset : 0 Timestamp : Sat Jan 1 00:00:00 2000 Creator Application : '' Creator version : Major: 0, Minor: 0 Creator OS : Unknown! Original disk size : 0 MB (0 Bytes) Current disk size : 0 MB (0 Bytes) Geometry : Cyl: 0, Hds: 0, Sctrs: 0 : = 0 MB (0 Bytes) Disk type : None Checksum : 0x0|0xffffffff (Bad!) UUID : 00000000-0000-0000-0000-000000000000 Saved state : No Hidden : 0 VHD Header Summary: ------------------- Cookie : Data offset (unusd) : 0 Table offset : 0 Header version : 0x00000000 Max BAT size : 0 Block size : 0 (0 MB) Parent name : Parent UUID : 00000000-0000-0000-0000-000000000000 Parent timestamp : Sat Jan 1 00:00:00 2000 Checksum : 0x0|0xffffffff (Bad!) I have a few VMs on this SR that have this issue. I have brought back about everything from backup except for one VM that I really ought to get back on. The with the issue is a vm-copy from another SR (full copy), and the same VM on the old SR is working fine. I don't really know where to look at, the documentation about the VHD and lvmoiscsi is rather scarce. If you have some hint, I'd be glad to try to dig into it. Thanks, DenisThanks, Julian On 16/05/11 15:31, Denis Cardon wrote:Hi everyone, this is my first post on this list, I hope I won't be off topic (Dave Scott's last post make me think that VDI issue are covered here). I think I have a VHD that has been victim of the bug covered in the Hotfix XS56EFP1006 (http://support.citrix.com/article/CTX129267). I've attached a /var/log/xensource output below. I'd like to know what are the option to get the data in that VDI? Is it possible to apply the fix on a XCP 1.0 pool? (2 servers, storage on lvmoicsi). Thanks for the help, Denis May 16 10:28:26 srvxen1 tapdisk[2893]: tapdisk-control: init, 10 x 4k buffers May 16 10:28:26 srvxen1 tapdisk[2893]: I/O queue driver: lio May 16 10:28:26 srvxen1 tapdisk[2893]: tapdisk-log: started, level 0 May 16 10:28:26 srvxen1 tapdisk[2893]: Loading driver 'vhd' for vbd 10 /dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-847c6b12-de04-446d-9551-6b8ebc4e01d8 0x00000000 May 16 10:28:26 srvxen1 tapdisk[2893]: libvhd::vhd_validate_footer: invalid footer cookie: May 16 10:28:26 srvxen1 tapdisk[2893]: libvhd::vhd_read_footer_at: /dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-847c6b12-de04-446d-9551-6b8ebc4e01d8: reading footer at 0x2017ffe00 failed: -22 May 16 10:28:26 srvxen1 tapdisk[2893]: libvhd::vhd_read: /dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-847c6b12-de04-446d-9551-6b8ebc4e01d8: read of 512 returned 0, errno: -22 May 16 10:28:26 srvxen1 tapdisk[2893]: libvhd::vhd_validate_footer: invalid footer cookie: May 16 10:28:26 srvxen1 tapdisk[2893]: libvhd::vhd_read_short_footer: /dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-847c6b12-de04-446d-9551-6b8ebc4e01d8: failed reading short footer: -22 May 16 10:28:26 srvxen1 tapdisk[2893]: libvhd::vhd_validate_footer: invalid footer cookie: May 16 10:28:26 srvxen1 tapdisk[2893]: libvhd::vhd_read_footer_at: /dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-847c6b12-de04-446d-9551-6b8ebc4e01d8: reading footer at 0x00000000 failed: -22 May 16 10:28:26 srvxen1 tapdisk[2893]: tap-err:__vhd_open: Unable to open [/dev/VG_XenStorage-f489b51d-7b20-62a7-d9f3-829a149cfb2e/VHD-847c6b12-de04-446d-9551-6b8ebc4e01d8] (-22)! May 16 10:28:26 srvxen1 tap-ctl: tap-err:tap_ctl_open: open failed, err -22 May 16 10:28:26 srvxen1 tapdisk[2893]: tapdisk-log: closing after 0 errors May 16 10:28:26 srvxen1 tapdisk[2893]: tapdisk-syslog: 6 messages, 450 bytes, xmits: 7, failed: 0, dropped: 0 May 16 10:28:26 srvxen1 tapdisk[2893]: tapdisk-control: draining 1 connections May 16 10:28:26 srvxen1 tapdisk[2893]: tapdisk-control: done May 16 10:28:26 srvxen1 fe: 2813 (/opt/xensource/sm/LVMoISCSISR <methodCall><methodName>vdi_activate</methodNam...) exitted with code 1 May 16 10:28:26 srvxen1 xapi: [error|srvxen1.pnrvf.local|1080378 unix-RPC|VM.start R:340b87ae50bc|xapi] Memory F 493288 KiB S 0 KiB T 12278 MiB -- Denis Cardon Tranquil IT Systems 44 bvd des pas enchantés 44230 Saint Sébastien sur Loire tel : +33 (0) 2.40.97.57.57 http://www.tranquil-it-systems.fr _______________________________________________ xen-api mailing list xen-api@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/mailman/listinfo/xen-api
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |