Am 01.08.2012 17:15, schrieb Paolo Bonzini: > Il 01/08/2012 16:59, Kevin Wolf ha scritto: >> Block jobs aren't really different from guests in that respect. Maybe >> the BB needs a second iostatus field that must explicitly be reset, and >> the old one keeps doing the stupid thing for compatibility's sake. > > Or the iostatus for the target can just reside in the BlockJob... :)
That wouldn't fix the problem in more than a single instance... > As much as I hate to invoke shortcuts, management may proceed without > human help only in the ENOSPC case, and ENOSPC can only happens on the > target. Humans usually look at dmesg to find the source. dmesg doesn't contain information about corrupted qcow2 images, Sheepdog error codes from the server, etc. Kevin
