From: Eric Blake <eblake@redhat.com>
To: Jeff Cody <jcody@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 2/3] block: resize backing image during active layer commit, if needed
Date: Thu, 23 Jan 2014 15:05:49 -0700 [thread overview]
Message-ID: <52E1923D.2080009@redhat.com> (raw)
In-Reply-To: <5cb7f2874a3525b2359739109c361f1b2640285a.1390513348.git.jcody@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]
On 01/23/2014 02:48 PM, Jeff Cody wrote:
> If the top image to commit is the active layer, and also larger than
> the base image, then an I/O error will likely be returned during
> block-commit.
>
> For instance, if we have a base image with a virtual size 10G, and a
> active layer image of size 20G, then committing the snapshot via
> 'block-commit' will likely fail.
>
> This will automatically attempt to resize the base image, if the
> active layer image to be committed is larger.
>
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> + if (length > base_length) {
> + if (bdrv_truncate(base, length) < 0) {
> + error_setg(errp, "Top image %s is larger than base image %s, and "
> + "resize of base image failed",
> + bs->filename, base->filename);
> + goto error_restore_flags;
> + }
> + } else if (length < 0) {
> + goto error_restore_flags;
> + }
> +
> +
> bdrv_ref(base);
> mirror_start_job(bs, base, speed, 0, 0,
> on_error, on_error, cb, opaque, errp,
> &commit_active_job_driver, false, base);
> + if (error_is_set(errp)) {
> + goto error_restore_flags;
If we get here, bdrv_truncate() succeeded at enlarging the base file. A
full rollback would imply adding a second bdrv_truncate() in the error
handling path to undo the growth back to the original size (of course,
ignoring failure to shrink). But that's more complex, and probably not
worth adding in (at any rate, leaving the base file larger doesn't
affect semantics of the bytes seen by the guest, and for file formats
that handle resizing via a sparse tail doesn't even consume much
storage). So my R-b stands.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-01-23 22:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 21:48 [Qemu-devel] [PATCH v3 0/3] block: commits of snapshots larger than backing files Jeff Cody
2014-01-23 21:48 ` [Qemu-devel] [PATCH v3 1/3] block: resize backing file image during offline commit, if necessary Jeff Cody
2014-01-23 22:00 ` Benoît Canet
2014-01-23 22:07 ` Eric Blake
2014-01-23 22:14 ` Jeff Cody
2014-01-23 22:35 ` Benoît Canet
2014-01-23 21:48 ` [Qemu-devel] [PATCH v3 2/3] block: resize backing image during active layer commit, if needed Jeff Cody
2014-01-23 22:05 ` Benoît Canet
2014-01-23 22:18 ` Jeff Cody
2014-01-23 22:05 ` Eric Blake [this message]
2014-01-23 21:48 ` [Qemu-devel] [PATCH v3 3/3] block: update block commit documentation regarding image truncation Jeff Cody
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=52E1923D.2080009@redhat.com \
--to=eblake@redhat.com \
--cc=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).