On 02/23/2016 05:27 PM, Fam Zheng wrote: > On Tue, 02/23 19:17, John Snow wrote: >> During incremental backups, if the target has a cluster size that is >> larger than the backup cluster size and we are backing up to a target >> that cannot (for whichever reason) pull clusters up from a backing image, >> we may inadvertantly create unusable incremental backup images. >>
>> + /* If there is no backing file on the target, we cannot rely on COW if
>> our
>> + * backup cluster size is smaller than the target cluster size. Even for
>> + * targets with a backing file, try to avoid COW if possible. */
>> + ret = bdrv_get_info(job->target, &bdi);
>> + if (ret < 0 && !target->backing) {
>> + error_setg_errno(errp, -ret,
>> + "Can't determine cluster size of target that has no backing
>> file. "
>> + "This may create an unusable destination image. Aborting.");
>
> Most error messages don't end with a period, but that's not a hard rule
> AFAICT.
Ah, but it is:
include/qapi/error.h:
* The resulting message should be a single phrase, with no newline or
* trailing punctuation.
* Please don't error_setg(&error_fatal, ...), use error_report() and
* exit(), because that's more obvious.
* Likewise, don't error_setg(&error_abort, ...), use assert().
*/
#define error_setg(errp, fmt, ...) \
The error message should be "Can't determine cluster size of target
without backing file"; everything else should be done with
error_append_hint(&errp, "Aborting, since this may create an unusable
destination image\n")
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
