From: Jeff Cody <jcody@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [qemu-kvm PATCH] block: vhdx - improve error message, and .bdrv_check implementation
Date: Tue, 17 Dec 2013 10:38:30 -0500 [thread overview]
Message-ID: <20131217153830.GC4333@localhost.localdomain> (raw)
In-Reply-To: <52B05819.8040708@redhat.com>
On Tue, Dec 17, 2013 at 06:56:41AM -0700, Eric Blake wrote:
> On 12/17/2013 03:33 AM, Jeff Cody wrote:
> > If there is a dirty log file to be replayed in a VHDX image, it is
> > replayed in .vhdx_open(). However, if the file is opened read-only,
> > then a somewhat cryptic error message results.
> >
> > This adds a more helpful error message for the user. If an image file
> > contains a log to be replayed, and is opened read-only, the user is
> > instructed to run 'qemu-img check -r all' on the image file.
> >
> > Running qemu-img check -r all will cause the image file to be opened
> > r/w, which will replay the log file. If a log file replay is detected,
> > this is flagged, and bdrv_check will increase the corruptions_fixed
> > count for the image.
>
> > + error_setg_errno(errp, EPERM,
> > + "VHDX image file '%s' opened read-only, but "
> > + "contains a log that needs replayed. To replay "
>
> s/replayed/replaying/
>
How about "to be replayed" instead? "Replaying", while correct, just
sounds a bit off to me.
> > + "the log, execute:\n qemu-img check -r all '%s'",
> > + bs->filename, bs->filename);
> > + goto exit;
>
> --
> Eric Blake eblake redhat com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
next prev parent reply other threads:[~2013-12-17 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 10:33 [Qemu-devel] [qemu-kvm PATCH] block: vhdx - improve error message, and .bdrv_check implementation Jeff Cody
2013-12-17 13:56 ` Eric Blake
2013-12-17 15:38 ` Jeff Cody [this message]
2013-12-17 15:44 ` Eric Blake
2013-12-18 13:52 ` Stefan Hajnoczi
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=20131217153830.GC4333@localhost.localdomain \
--to=jcody@redhat.com \
--cc=eblake@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).