From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:51891)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1SyJdP-00045I-8X
	for qemu-devel@nongnu.org; Mon, 06 Aug 2012 05:30:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1SyJdN-0001w9-Dx
	for qemu-devel@nongnu.org; Mon, 06 Aug 2012 05:29:59 -0400
Received: from mx1.redhat.com ([209.132.183.28]:53647)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1SyJdN-0001vt-5j
	for qemu-devel@nongnu.org; Mon, 06 Aug 2012 05:29:57 -0400
Message-ID: <501F8E8F.5000509@redhat.com>
Date: Mon, 06 Aug 2012 11:29:51 +0200
From: Kevin Wolf <kwolf@redhat.com>
MIME-Version: 1.0
References: <1343127865-16608-1-git-send-email-pbonzini@redhat.com>
	<1343127865-16608-14-git-send-email-pbonzini@redhat.com>
	<5019016F.1050909@redhat.com> <50191044.7070109@redhat.com>
	<501917CB.1060704@redhat.com> <50191C97.8000005@redhat.com>
	<50191FA7.1070309@redhat.com> <50192182.8070509@redhat.com>
	<50192A8D.3000309@redhat.com> <50192D49.6030504@redhat.com>
	<501936C9.40006@redhat.com> <50193E84.7050503@redhat.com>
	<5019445F.9010308@redhat.com> <501947FD.2080201@redhat.com>
In-Reply-To: <501947FD.2080201@redhat.com>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH 13/47] block: introduce block job error
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: jcody@redhat.com, eblake@redhat.com, qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com

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