Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1775480

Summary: Creating luks-inside-qcow2 images with cluster_size=2k/4k will get a corrupted image
Product: Red Hat Enterprise Linux Advanced Virtualization Reporter: Tingting Mao <timao>
Component: qemu-kvmAssignee: Virtualization Maintenance <virt-maint>
qemu-kvm sub component: Storage QA Contact: Virtualization Bugs <virt-bugs>
Status: CLOSED DUPLICATE Docs Contact:
Severity: unspecified    
Priority: high CC: areis, coli, jinzhao, junzhang, qzhang, virt-maint, xuwei
Version: 8.1Keywords: Regression
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-25 15:34:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tingting Mao 2019-11-22 04:51:44 UTC 
This bug was initially created as a copy of Bug #1775462

I am copying this bug because: 



Description of problem:
As subject. For luks-inside-qcow2 images with remain cluster_size, like 512, 1k, ...2M , there is no the issue. And for plain qcow2 without encryption, there is no the issue. 


Version-Release number of selected component (if applicable):
qemu-kvm-4.2.0-1.module+el8.2.0+4793+b09dd2fb
kernel-4.18.0-148.el8.x86_64


How reproducible:
100%


Steps to Reproduce:
Scenario 1(With cluster_size=2k)
# qemu-img create --object secret,id=cluster_encrypt0,data=redhat -f qcow2 -o cluster_size=2k,encrypt.format=luks,encrypt.key-secret=cluster_encrypt0 cluster_size_check.qcow2 1G

# qemu-img check --object secret,id=cluster_encrypt0,data=redhat 'json:{"driver": "qcow2", "encrypt.format": "luks", "encrypt.key-secret": "cluster_encrypt0", "file.driver": "file", "file.filename": "cluster_size_check.qcow2"}'
ERROR: counting reference for region exceeding the end of the file by one cluster or more: offset 0x5800 size 0x1f9000
Leaked cluster 11 refcount=1 reference=0
Leaked cluster 12 refcount=1 reference=0
Leaked cluster 13 refcount=1 reference=0
Leaked cluster 14 refcount=1 reference=0
Leaked cluster 15 refcount=1 reference=0
Leaked cluster 16 refcount=1 reference=0
Leaked cluster 17 refcount=1 reference=0
Leaked cluster 18 refcount=1 reference=0
Leaked cluster 19 refcount=1 reference=0
Leaked cluster 20 refcount=1 reference=0
Leaked cluster 21 refcount=1 reference=0
Leaked cluster 22 refcount=1 reference=0
Leaked cluster 23 refcount=1 reference=0
Leaked cluster 24 refcount=1 reference=0
Leaked cluster 25 refcount=1 reference=0
Leaked cluster 26 refcount=1 reference=0
Leaked cluster 27 refcount=1 reference=0
Leaked cluster 28 refcount=1 reference=0
Leaked cluster 29 refcount=1 reference=0
Leaked cluster 30 refcount=1 reference=0
Leaked cluster 31 refcount=1 reference=0
Leaked cluster 32 refcount=1 reference=0
Leaked cluster 33 refcount=1 reference=0
Leaked cluster 34 refcount=1 reference=0
Leaked cluster 35 refcount=1 reference=0
Leaked cluster 36 refcount=1 reference=0
Leaked cluster 37 refcount=1 reference=0
Leaked cluster 38 refcount=1 reference=0
Leaked cluster 39 refcount=1 reference=0
Leaked cluster 40 refcount=1 reference=0
Leaked cluster 41 refcount=1 reference=0
Leaked cluster 42 refcount=1 reference=0
Leaked cluster 43 refcount=1 reference=0
Leaked cluster 44 refcount=1 reference=0
Leaked cluster 45 refcount=1 reference=0
Leaked cluster 46 refcount=1 reference=0
Leaked cluster 47 refcount=1 reference=0
Leaked cluster 48 refcount=1 reference=0
Leaked cluster 49 refcount=1 reference=0
Leaked cluster 50 refcount=1 reference=0
Leaked cluster 51 refcount=1 reference=0
Leaked cluster 52 refcount=1 reference=0
Leaked cluster 53 refcount=1 reference=0
Leaked cluster 54 refcount=1 reference=0
Leaked cluster 55 refcount=1 reference=0
Leaked cluster 56 refcount=1 reference=0
Leaked cluster 57 refcount=1 reference=0
Leaked cluster 58 refcount=1 reference=0
Leaked cluster 59 refcount=1 reference=0
Leaked cluster 60 refcount=1 reference=0
Leaked cluster 61 refcount=1 reference=0
Leaked cluster 62 refcount=1 reference=0
Leaked cluster 63 refcount=1 reference=0
Leaked cluster 64 refcount=1 reference=0
Leaked cluster 65 refcount=1 reference=0
Leaked cluster 66 refcount=1 reference=0
Leaked cluster 67 refcount=1 reference=0
Leaked cluster 68 refcount=1 reference=0
Leaked cluster 69 refcount=1 reference=0
Leaked cluster 70 refcount=1 reference=0
Leaked cluster 71 refcount=1 reference=0
Leaked cluster 72 refcount=1 reference=0
Leaked cluster 73 refcount=1 reference=0
Leaked cluster 74 refcount=1 reference=0
Leaked cluster 75 refcount=1 reference=0
Leaked cluster 76 refcount=1 reference=0
Leaked cluster 77 refcount=1 reference=0
Leaked cluster 78 refcount=1 reference=0
Leaked cluster 79 refcount=1 reference=0
Leaked cluster 80 refcount=1 reference=0
Leaked cluster 81 refcount=1 reference=0
Leaked cluster 82 refcount=1 reference=0
Leaked cluster 83 refcount=1 reference=0
Leaked cluster 84 refcount=1 reference=0
Leaked cluster 85 refcount=1 reference=0
Leaked cluster 86 refcount=1 reference=0
Leaked cluster 87 refcount=1 reference=0
Leaked cluster 88 refcount=1 reference=0
Leaked cluster 89 refcount=1 reference=0
Leaked cluster 90 refcount=1 reference=0
Leaked cluster 91 refcount=1 reference=0
Leaked cluster 92 refcount=1 reference=0
Leaked cluster 93 refcount=1 reference=0
Leaked cluster 94 refcount=1 reference=0
Leaked cluster 95 refcount=1 reference=0
Leaked cluster 96 refcount=1 reference=0
Leaked cluster 97 refcount=1 reference=0
Leaked cluster 98 refcount=1 reference=0
Leaked cluster 99 refcount=1 reference=0
Leaked cluster 100 refcount=1 reference=0
Leaked cluster 101 refcount=1 reference=0
Leaked cluster 102 refcount=1 reference=0
Leaked cluster 103 refcount=1 reference=0
Leaked cluster 104 refcount=1 reference=0
Leaked cluster 105 refcount=1 reference=0
Leaked cluster 106 refcount=1 reference=0
Leaked cluster 107 refcount=1 reference=0
Leaked cluster 108 refcount=1 reference=0
Leaked cluster 109 refcount=1 reference=0
Leaked cluster 110 refcount=1 reference=0
Leaked cluster 111 refcount=1 reference=0
Leaked cluster 112 refcount=1 reference=0
Leaked cluster 113 refcount=1 reference=0
Leaked cluster 114 refcount=1 reference=0
Leaked cluster 115 refcount=1 reference=0
Leaked cluster 116 refcount=1 reference=0
Leaked cluster 117 refcount=1 reference=0
Leaked cluster 118 refcount=1 reference=0
Leaked cluster 119 refcount=1 reference=0
Leaked cluster 120 refcount=1 reference=0
Leaked cluster 121 refcount=1 reference=0
Leaked cluster 122 refcount=1 reference=0
Leaked cluster 123 refcount=1 reference=0
Leaked cluster 124 refcount=1 reference=0
Leaked cluster 125 refcount=1 reference=0
Leaked cluster 126 refcount=1 reference=0
Leaked cluster 127 refcount=1 reference=0
Leaked cluster 128 refcount=1 reference=0
Leaked cluster 129 refcount=1 reference=0
Leaked cluster 130 refcount=1 reference=0
Leaked cluster 131 refcount=1 reference=0
Leaked cluster 132 refcount=1 reference=0
Leaked cluster 133 refcount=1 reference=0
Leaked cluster 134 refcount=1 reference=0
Leaked cluster 135 refcount=1 reference=0
Leaked cluster 136 refcount=1 reference=0
Leaked cluster 137 refcount=1 reference=0

1 errors were found on the image.
Data may be corrupted, or further writes to the image may corrupt it.

127 leaked clusters were found on the image.
This means waste of disk space, but no harm to data.
Image end offset: 282624


Scenario 2(With cluster_size=4K)
# qemu-img create --object secret,id=cluster_encrypt0,data=redhat -f qcow2 -o cluster_size=4k,encrypt.format=luks,encrypt.key-secret=cluster_encrypt0 cluster_size_check.qcow2 1G

# qemu-img check --object secret,id=cluster_encrypt0,data=redhat 'json:{"driver": "qcow2", "encrypt.format": "luks", "encrypt.key-secret": "cluster_encrypt0", "file.driver": "file", "file.filename": "cluster_size_check.qcow2"}'
ERROR: counting reference for region exceeding the end of the file by one cluster or more: offset 0x4000 size 0x1f9000
Leaked cluster 4 refcount=1 reference=0
Leaked cluster 5 refcount=1 reference=0
Leaked cluster 6 refcount=1 reference=0
Leaked cluster 7 refcount=1 reference=0
Leaked cluster 8 refcount=1 reference=0
Leaked cluster 9 refcount=1 reference=0
Leaked cluster 10 refcount=1 reference=0
Leaked cluster 11 refcount=1 reference=0
Leaked cluster 12 refcount=1 reference=0
Leaked cluster 13 refcount=1 reference=0
Leaked cluster 14 refcount=1 reference=0
Leaked cluster 15 refcount=1 reference=0
Leaked cluster 16 refcount=1 reference=0
Leaked cluster 17 refcount=1 reference=0
Leaked cluster 18 refcount=1 reference=0
Leaked cluster 19 refcount=1 reference=0
Leaked cluster 20 refcount=1 reference=0
Leaked cluster 21 refcount=1 reference=0
Leaked cluster 22 refcount=1 reference=0
Leaked cluster 23 refcount=1 reference=0
Leaked cluster 24 refcount=1 reference=0
Leaked cluster 25 refcount=1 reference=0
Leaked cluster 26 refcount=1 reference=0
Leaked cluster 27 refcount=1 reference=0
Leaked cluster 28 refcount=1 reference=0
Leaked cluster 29 refcount=1 reference=0
Leaked cluster 30 refcount=1 reference=0
Leaked cluster 31 refcount=1 reference=0
Leaked cluster 32 refcount=1 reference=0
Leaked cluster 33 refcount=1 reference=0
Leaked cluster 34 refcount=1 reference=0
Leaked cluster 35 refcount=1 reference=0
Leaked cluster 36 refcount=1 reference=0
Leaked cluster 37 refcount=1 reference=0
Leaked cluster 38 refcount=1 reference=0
Leaked cluster 39 refcount=1 reference=0
Leaked cluster 40 refcount=1 reference=0
Leaked cluster 41 refcount=1 reference=0
Leaked cluster 42 refcount=1 reference=0
Leaked cluster 43 refcount=1 reference=0
Leaked cluster 44 refcount=1 reference=0
Leaked cluster 45 refcount=1 reference=0
Leaked cluster 46 refcount=1 reference=0
Leaked cluster 47 refcount=1 reference=0
Leaked cluster 48 refcount=1 reference=0
Leaked cluster 49 refcount=1 reference=0
Leaked cluster 50 refcount=1 reference=0
Leaked cluster 51 refcount=1 reference=0
Leaked cluster 52 refcount=1 reference=0
Leaked cluster 53 refcount=1 reference=0
Leaked cluster 54 refcount=1 reference=0
Leaked cluster 55 refcount=1 reference=0
Leaked cluster 56 refcount=1 reference=0
Leaked cluster 57 refcount=1 reference=0
Leaked cluster 58 refcount=1 reference=0
Leaked cluster 59 refcount=1 reference=0
Leaked cluster 60 refcount=1 reference=0
Leaked cluster 61 refcount=1 reference=0
Leaked cluster 62 refcount=1 reference=0
Leaked cluster 63 refcount=1 reference=0
Leaked cluster 64 refcount=1 reference=0
Leaked cluster 65 refcount=1 reference=0
Leaked cluster 66 refcount=1 reference=0
Leaked cluster 67 refcount=1 reference=0

1 errors were found on the image.
Data may be corrupted, or further writes to the image may corrupt it.

64 leaked clusters were found on the image.
This means waste of disk space, but no harm to data.
Image end offset: 278528


Actual results:
As above, the image is corrupted.


Expected results:
Image is well. There is no error in the image.


Additional info:
1. Tried with all the supported cluster_size via below script. Only 2k and 4k hit the issue.

#!/bin/bash

for ((i=9; i<=21; i++))
do
    cluster=$(( 2 ** ${i} ))
    qemu-img create --object secret,id=cluster_encrypt0,data=redhat -f qcow2 -o cluster_size=${cluster},encrypt.format=luks,encrypt.key-secret=cluster_encrypt0 cluster_size_check.qcow2 1G > /dev/null
    qemu-img check --object secret,id=cluster_encrypt0,data=redhat 'json:{"driver": "qcow2", "encrypt.format": "luks", "encrypt.key-secret": "cluster_encrypt0", "file.driver": "file", "file.filename": "cluster_size_check.qcow2"}' > /dev/null 2>&1
    if [ $? != 0 ]; then
        echo "Check failed with cluster_size=${cluster}!"
    fi
done

# sh test.sh 
Check failed with cluster_size=2048!
Check failed with cluster_size=4096!

2. There is no the issue for plain qcow2 images without encryption.

#!/bin/bash

for ((i=9; i<=21; i++))
do
    cluster=$(( 2 ** ${i} ))
    qemu-img create -f qcow2 -o cluster_size=${cluster} cluster_size_check.qcow2 1G > /dev/null
    qemu-img check cluster_size_check.qcow2 > /dev/null 2>&1
    if [ $? != 0 ]; then
        echo "Check failed with cluster_size=${cluster}!"
    fi
done

# sh test.sh 
# echo $?
0
Comment 5 Ademar Reis 2019-11-25 15:32:15 UTC 
*** Bug 1775462 has been marked as a duplicate of this bug. ***
Comment 6 Ademar Reis 2019-11-25 15:34:06 UTC 
Closed the wrong one, sorry for the noise.

*** This bug has been marked as a duplicate of bug 1775462 ***