qemu-block
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-block] qemu image corrupted, can not repair


From: John Snow
Subject: Re: [Qemu-block] qemu image corrupted, can not repair
Date: Fri, 25 May 2018 16:11:42 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0


On 05/25/2018 08:47 AM, Bilhan Karaoren (Garanti Teknoloji) wrote:
> Hi,
> 
> I experience a corrupted qcow2 image.
> 

How did the corruption occur? What version of QEMU are you using?

>  
> 
> *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?
> 

Very likely not. It looks like the metadata information for where the
data is laid out in the image has been overwritten.

>  
> 
> *#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.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]