From: xuanmao_001 <xuanmao_001@163.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
qemu-discuss <qemu-discuss@nongnu.org>
Subject: Re: [Qemu-devel] qemu-img convert will increase the VM image
Date: Wed, 11 Sep 2013 16:50:02 +0800 [thread overview]
Message-ID: <2013091116500290678419@163.com> (raw)
In-Reply-To: 20130911082817.GB2305@dhcp-200-207.str.redhat.com
[-- Attachment #1: Type: text/plain, Size: 6711 bytes --]
the first 30lines output from orignal image:
1 [ 0] 128/ 4096000 sectors allocated at offset 0.000000 bytes (1)
2 [ 65536] 1920/ 4095872 sectors not allocated at offset 64 KiB (0)
3 [ 1048576] 128/ 4093952 sectors allocated at offset 1 MiB (1)
4 [ 1114112] 128/ 4093824 sectors allocated at offset 1 MiB (1)
5 [ 1179648] 128/ 4093696 sectors allocated at offset 1 MiB (1)
6 [ 1245184] 128/ 4093568 sectors allocated at offset 1 MiB (1)
7 [ 1310720] 256/ 4093440 sectors not allocated at offset 1 MiB (0)
8 [ 1441792] 128/ 4093184 sectors allocated at offset 1 MiB (1)
9 [ 1507328] 1792/ 4093056 sectors not allocated at offset 1 MiB (0)
10 [ 2424832] 128/ 4091264 sectors allocated at offset 2 MiB (1)
11 [ 2490368] 2560/ 4091136 sectors not allocated at offset 2 MiB (0)
12 [ 3801088] 128/ 4088576 sectors allocated at offset 4 MiB (1)
13 [ 3866624] 512/ 4088448 sectors allocated at offset 4 MiB (1)
14 [ 4128768] 128/ 4087936 sectors allocated at offset 4 MiB (1)
15 [ 4194304] 128/ 4087808 sectors allocated at offset 4 MiB (1)
16 [ 4259840] 128/ 4087680 sectors allocated at offset 4 MiB (1)
17 [ 4325376] 128/ 4087552 sectors allocated at offset 4 MiB (1)
18 [ 4390912] 128/ 4087424 sectors allocated at offset 4 MiB (1)
19 [ 4456448] 128/ 4087296 sectors allocated at offset 4 MiB (1)
20 [ 4521984] 128/ 4087168 sectors allocated at offset 4 MiB (1)
21 [ 4587520] 128/ 4087040 sectors allocated at offset 4 MiB (1)
22 [ 4653056] 128/ 4086912 sectors allocated at offset 4 MiB (1)
23 [ 4718592] 128/ 4086784 sectors allocated at offset 4 MiB (1)
24 [ 4784128] 640/ 4086656 sectors allocated at offset 5 MiB (1)
25 [ 5111808] 128/ 4086016 sectors allocated at offset 5 MiB (1)
26 [ 5177344] 128/ 4085888 sectors allocated at offset 5 MiB (1)
27 [ 5242880] 4096/ 4085760 sectors not allocated at offset 5 MiB (0)
28 [ 7340032] 128/ 4081664 sectors allocated at offset 7 MiB (1)
29 [ 7405568] 128/ 4081536 sectors allocated at offset 7 MiB (1)
30 [ 7471104] 128/ 4081408 sectors allocated at offset 7 MiB (1)
the first 30lines output from modify image:
1 [ 0] 128/ 4096000 sectors allocated at offset 0.000000 bytes (1)
2 [ 65536] 1920/ 4095872 sectors not allocated at offset 64 KiB (0)
3 [ 1048576] 512/ 4093952 sectors allocated at offset 1 MiB (1)
4 [ 1310720] 256/ 4093440 sectors not allocated at offset 1 MiB (0)
5 [ 1441792] 128/ 4093184 sectors allocated at offset 1 MiB (1)
6 [ 1507328] 1792/ 4093056 sectors not allocated at offset 1 MiB (0)
7 [ 2424832] 128/ 4091264 sectors allocated at offset 2 MiB (1)
8 [ 2490368] 2560/ 4091136 sectors not allocated at offset 2 MiB (0)
9 [ 3801088] 2816/ 4088576 sectors allocated at offset 4 MiB (1)
10 [ 5242880] 4096/ 4085760 sectors not allocated at offset 5 MiB (0)
11 [ 7340032] 4224/ 4081664 sectors allocated at offset 7 MiB (1)
12 [ 9502720] 128/ 4077440 sectors not allocated at offset 9 MiB (0)
13 [ 9568256] 896/ 4077312 sectors allocated at offset 9 MiB (1)
14 [ 10027008] 896/ 4076416 sectors not allocated at offset 10 MiB (0)
15 [ 10485760] 8320/ 4075520 sectors allocated at offset 10 MiB (1)
16 [ 14745600] 1920/ 4067200 sectors not allocated at offset 14 MiB (0)
17 [ 15728640] 4480/ 4065280 sectors allocated at offset 15 MiB (1)
18 [ 18022400] 16000/ 4060800 sectors not allocated at offset 17 MiB (0)
19 [ 26214400] 128/ 4044800 sectors allocated at offset 25 MiB (1)
20 [ 26279936] 12160/ 4044672 sectors not allocated at offset 25 MiB (0)
21 [ 32505856] 12416/ 4032512 sectors allocated at offset 31 MiB (1)
22 [ 38862848] 3840/ 4020096 sectors not allocated at offset 37 MiB (0)
23 [ 40828928] 1280/ 4016256 sectors allocated at offset 39 MiB (1)
24 [ 41484288] 384/ 4014976 sectors not allocated at offset 40 MiB (0)
25 [ 41680896] 128/ 4014592 sectors allocated at offset 40 MiB (1)
26 [ 41746432] 7040/ 4014464 sectors not allocated at offset 40 MiB (0)
27 [ 45350912] 640/ 4007424 sectors allocated at offset 43 MiB (1)
28 [ 45678592] 7040/ 4006784 sectors not allocated at offset 44 MiB (0)
29 [ 49283072] 128/ 3999744 sectors allocated at offset 47 MiB (1)
30 [ 49348608] 384/ 3999616 sectors not allocated at offset 47 MiB (0)
they are different.
what caused the problem ?
xuanmao_001
From: Kevin Wolf
Date: 2013-09-11 16:28
To: xuanmao_001
CC: qemu-devel; qemu-discuss
Subject: Re: qemu-img convert will increase the VM image
Am 11.09.2013 um 09:14 hat xuanmao_001 geschrieben:
> Hi, all:
>
> I have question about qemu-img convert ...
>
> I have a orignal image with following information:
> # qemu-img info ori.qcow2
> image: ori.qcow2
> file format: qcow2
> virtual size: 2.0G (2097152000 bytes)
> disk size: 308M
> cluster_size: 65536
>
> when I executed with "qemu-img convert -f qcow2 -O qcow2 ori.qcow2 new.qcow2"
> the new.qcow2 like following:
> # qemu-img info new.qcow2
> image: new.qcow2
> file format: qcow2
> virtual size: 2.0G (2097152000 bytes)
> disk size: 748M
> cluster_size: 65536
>
> so, my question is why the image size increased after my operation?
You can try comparing the output of the qemu-io 'map' command for both
images.
Kevin
[-- Attachment #2: Type: text/html, Size: 20908 bytes --]
prev parent reply other threads:[~2013-09-11 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 7:14 [Qemu-devel] qemu-img convert will increase the VM image xuanmao_001
2013-09-11 8:28 ` Kevin Wolf
2013-09-11 8:50 ` xuanmao_001 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2013091116500290678419@163.com \
--to=xuanmao_001@163.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.