blob: b894fe605519e2cc2a11b3c381957d89c220799a (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
mistranslation: 0.848
semantic: 0.819
graphic: 0.816
device: 0.767
network: 0.688
other: 0.660
socket: 0.593
instruction: 0.581
boot: 0.544
vnc: 0.519
KVM: 0.414
assembly: 0.271
`qemu-img info` reports an incorrect actual-size when the underlying posix filesystem has transparent compression
qemu-img info reports the same thing as `du`*1024:
$ qemu-img info --output json ./my.qcow2 | jq '."actual-size"'
558619648
$ du ./my.qcow2
545527 ./my.qcow2
$ echo $((558619648 / 545527))
1024
and this is correct in terms of bytes on disk, but due to transparent compression implemented by the filesystem, it is not the actual byte count:
$ du -h --apparent-size ./my.qcow2
1346568192 my.qcow2
But that’s the point of that field, to show the amount of space used by the image on the host.
The man page documents it as: “disk size: How much space the image file occupies on the host file system (may be shown as 0 if this information is unavailable, e.g. because there is no file system)”, and the QAPI definition of ImageInfo documents the actual-size field as “actual size on disk in bytes of the image”.
So it is documented as and intended to be the number of bytes used, not the length of the file.
Max
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1881648
|