From: Fam Zheng <famz@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/3] block: resize backing file image during offline commit, if necessary
Date: Wed, 22 Jan 2014 09:58:15 +0800 [thread overview]
Message-ID: <20140122015815.GE24604@T430.redhat.com> (raw)
In-Reply-To: <afa1989a2f131af7fd6657608b1adc6419eb5eb1.1390321064.git.jcody@redhat.com>
On Tue, 01/21 11:31, Jeff Cody wrote:
> Currently, if an image file is logically larger than its backing file,
> commiting it via 'qemu-img commit' will fail.
>
> For instance, if we have a base image with a virtual size 10G, and a
> snapshot image of size 20G, then committing the snapshot offline with
> 'qemu-img commit' will likely fail.
>
> This will automatically attempt to resize the base image, if the
> snapshot image to be committed is larger.
>
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> ---
> block.c | 23 ++++++++++++++++++++---
> 1 file changed, 20 insertions(+), 3 deletions(-)
>
> diff --git a/block.c b/block.c
> index 64e7d22..dea7591 100644
> --- a/block.c
> +++ b/block.c
> @@ -1876,10 +1876,10 @@ int bdrv_check(BlockDriverState *bs, BdrvCheckResult *res, BdrvCheckMode fix)
> int bdrv_commit(BlockDriverState *bs)
> {
> BlockDriver *drv = bs->drv;
> - int64_t sector, total_sectors;
> + int64_t sector, total_sectors, length, backing_length;
> int n, ro, open_flags;
> int ret = 0;
> - uint8_t *buf;
> + uint8_t *buf = NULL;
> char filename[PATH_MAX];
>
> if (!drv)
> @@ -1904,7 +1904,24 @@ int bdrv_commit(BlockDriverState *bs)
> }
> }
>
> - total_sectors = bdrv_getlength(bs) >> BDRV_SECTOR_BITS;
> + length = bdrv_getlength(bs);
> + backing_length = bdrv_getlength(bs->backing_hd);
> +
> + if (length < 0 || backing_length < 0) {
> + goto ro_cleanup;
> + }
> +
> + /* If our top snapshot is larger than the backing file image,
> + * grow the backing file image if possible. If not possible,
> + * we must return an error */
> + if (length > backing_length) {
> + ret = bdrv_truncate(bs->backing_hd, length);
> + if (ret < 0) {
> + goto ro_cleanup;
> + }
> + }
> +
> + total_sectors = length >> BDRV_SECTOR_BITS;
> buf = g_malloc(COMMIT_BUF_SECTORS * BDRV_SECTOR_SIZE);
>
> for (sector = 0; sector < total_sectors; sector += n) {
> --
> 1.8.3.1
>
Reviewed-by: Fam Zheng <famz@redhat.com>
next prev parent reply other threads:[~2014-01-22 1:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 16:31 [Qemu-devel] [PATCH v2 0/3] block: commits of snapshots larger than backing files Jeff Cody
2014-01-21 16:31 ` [Qemu-devel] [PATCH v2 1/3] block: resize backing file image during offline commit, if necessary Jeff Cody
2014-01-21 16:41 ` Eric Blake
2014-01-22 1:58 ` Fam Zheng [this message]
2014-01-21 16:31 ` [Qemu-devel] [PATCH v2 2/3] block: resize backing image during active layer commit, if needed Jeff Cody
2014-01-21 17:00 ` Eric Blake
2014-01-22 1:54 ` Fam Zheng
2014-01-22 4:28 ` Jeff Cody
2014-01-21 16:31 ` [Qemu-devel] [PATCH v2 3/3] block: update block commit documentation regarding image truncation Jeff Cody
2014-01-21 16:37 ` Eric Blake
2014-01-22 2:03 ` Fam Zheng
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=20140122015815.GE24604@T430.redhat.com \
--to=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).