|
From: | Bilhan Karaoren (Garanti Teknoloji) |
Subject: | [Qemu-block] qemu image corrupted, can not repair |
Date: | Fri, 25 May 2018 12:47:50 +0000 |
Hi, I experience a corrupted qcow2 image.
qemu-img info /dev/0d0496cf-3ff3-4c37-9314-77f2243b4efa/b363f461-dbf2-4daa-950b-f6f1d89cd0f2 image: /dev/0d0496cf-3ff3-4c37-9314-77f2243b4efa/b363f461-dbf2-4daa-950b-f6f1d89cd0f2 file format: qcow2 virtual size: 500G (536870912000 bytes) disk size: 0 cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: true It exist with the following information. qemu-img check -r all /dev/0d0496cf-3ff3-4c37-9314-77f2243b4efa/b363f461-dbf2-4daa-950b-f6f1d89cd0f2 tcmalloc: large alloc 560532619264 bytes == 0x5558971ba000 @ 0x7f2b9c015bf3 0x7f2b9c037488 0x7f2b9bb39c56 0x5558947f06d1 0x5558947f2ca3 0x5558947f2e0d 0x5558947f325d 0x5558947f3c16 0x5558947ec151 0x5558947c53ab
0x5558947c75bb 0x5558947c0019 0x7f2b9a194c05 0x5558947c071c ERROR l2_offset=41412c70726e00: Table is not cluster aligned; L1 entry corrupted tcmalloc: large alloc 836894392320 bytes == 0x55db3a01a000 @ 0x7f2b9c015bf3 0x7f2b9c037488 0x7f2b9bb39c56 0x5558947f06d1 0x5558947f2ca3 0x5558947f2e0d 0x5558947f325d 0x5558947f3c16 0x5558947ec151 0x5558947c53ab
0x5558947c75bb 0x5558947c0019 0x7f2b9a194c05 0x5558947c071c ERROR l2_offset=616d652c6e6c00: Table is not cluster aligned; L1 entry corrupted ERROR l2_offset=a4141412c6200: Table is not cluster aligned; L1 entry corrupted tcmalloc: large alloc 1046117990400 bytes == 0x569e454ca000 @ 0x7f2b9c015bf3 0x7f2b9c0374cc 0x7f2b9bb39c56 0x5558947f06d1 0x5558947f2ca3 0x5558947f2e0d 0x5558947f325d 0x5558947f3c16 0x5558947ec151 0x5558947c53ab
0x5558947c75bb 0x5558947c0019 0x7f2b9a194c05 0x5558947c071c ERROR l2_offset=6d616e642c6e00: Table is not cluster aligned; L1 entry corrupted ERROR cluster 525682632547 refcount=0 reference=1 Rebuilding refcount structure ERROR writing refblock: No space left on device qemu-img: Check failed: No space left on device Is there any way to recover this image? #lvdisplay /dev/0d0496cf-3ff3-4c37-9314-77f2243b4efa/b363f461-dbf2-4daa-950b-f6f1d89cd0f2 --- Logical volume --- LV Path /dev/0d0496cf-3ff3-4c37-9314-77f2243b4efa/b363f461-dbf2-4daa-950b-f6f1d89cd0f2 LV Name b363f461-dbf2-4daa-950b-f6f1d89cd0f2 VG Name 0d0496cf-3ff3-4c37-9314-77f2243b4efa LV UUID Qvm9qy-pO1o-oUS7-dzLz-xbU5-Mq0Y-CRgTD8 LV Write Access read/write LV Creation host, time gbrhvt04, 2018-04-25 16:36:08 +0300 LV Status available # open 0 LV Size 36.00 GiB Current LE 288 Segments 4 Allocation inherit Read ahead sectors auto - currently set to 8192 Block device 253:30 Regards, Bilhan. This message and attachments are confidential and intended solely for the individual(s) stated in this message. If you received this message although you are not the addressee, you are responsible to keep the message confidential. The sender has no responsibility for the accuracy or correctness of the information in the message and its attachments. Our company shall have no liability for any changes or late receiving, loss of integrity and confidentiality, viruses and any damages caused in anyway to your computer system. |
[Prev in Thread] | Current Thread | [Next in Thread] |