From: Jeff Cody <jcody@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/3] block: resize backing image during active layer commit, if needed
Date: Tue, 21 Jan 2014 23:28:14 -0500 [thread overview]
Message-ID: <20140122042814.GB13722@localhost.localdomain> (raw)
In-Reply-To: <20140122015426.GD24604@T430.redhat.com>
On Wed, Jan 22, 2014 at 09:54:26AM +0800, Fam Zheng wrote:
> On Tue, 01/21 11:31, 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>
> > ---
> > block/mirror.c | 36 ++++++++++++++++++++++++++++++++++++
> > 1 file changed, 36 insertions(+)
> >
> > diff --git a/block/mirror.c b/block/mirror.c
> > index 2932bab..528b61a 100644
> > --- a/block/mirror.c
> > +++ b/block/mirror.c
> > @@ -630,11 +630,47 @@ void commit_active_start(BlockDriverState *bs, BlockDriverState *base,
> > BlockDriverCompletionFunc *cb,
> > void *opaque, Error **errp)
> > {
> > + int64_t length, base_length;
> > + int orig_base_flags;
> > +
> > + orig_base_flags = bdrv_get_flags(base);
> > +
> > if (bdrv_reopen(base, bs->open_flags, errp)) {
> > return;
> > }
> > +
> > + length = bdrv_getlength(bs);
> > + base_length = bdrv_getlength(base);
> > +
> > + if (length < 0 || base_length < 0) {
>
> I prefer to add an error to errp here, at least tell which bdrv_getlength
> failed helps.
>
OK, I can do that.
> > + goto error_restore_flags;
> > + }
> > +
> > + 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;
> > + }
> > +
> > + return;
> > +
> > +error_restore_flags:
> > + /* ignore error and errp for bdrv_reopen, because we want to propagate
> > + * the original error */
> > + bdrv_reopen(base, orig_base_flags, NULL);
>
> Well, I hope this never fail. (But if it does, should we do anything else than
> ignoring it?)
>
Me too :) There isn't a lot we can do but ignore it; the original
error that lead us here is most likely more important and informative
than the reopen error, so I don't think it makes sense to override
errp. And failing to restore the original flags is likely not
catastrophic (but symptomatic).
>
> > + return;
> > }
> > --
> > 1.8.3.1
> >
next prev parent reply other threads:[~2014-01-22 4:28 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
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 [this message]
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=20140122042814.GB13722@localhost.localdomain \
--to=jcody@redhat.com \
--cc=famz@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).