From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43381) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZpBIa-0000bW-3Y for qemu-devel@nongnu.org; Thu, 22 Oct 2015 04:32:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZpBIZ-0007IL-Cx for qemu-devel@nongnu.org; Thu, 22 Oct 2015 04:32:36 -0400 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:42155 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZpBIZ-0007I9-4K for qemu-devel@nongnu.org; Thu, 22 Oct 2015 04:32:35 -0400 References: <1445501858-18790-1-git-send-email-famz@redhat.com> From: Peter Lieven Message-ID: <56289F1C.2040605@kamp.de> Date: Thu, 22 Oct 2015 10:32:28 +0200 MIME-Version: 1.0 In-Reply-To: <1445501858-18790-1-git-send-email-famz@redhat.com> Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/2] Fix werror=enospc for qcow2 on iscsi List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Fam Zheng , qemu-devel@nongnu.org Cc: Kevin Wolf , Paolo Bonzini , qemu-block@nongnu.org, Ronnie Sahlberg Am 22.10.2015 um 10:17 schrieb Fam Zheng: > When qcow2 is created on iscsi target with a virtual size greater than physical > capacity of the LUN, over time it's possible that guest fills too much data and > at that point, new clusters in qcow2 will be allocated beyond the end of disk. Why would you want to put a QCOW2 on a fixed size block device? Anyway, I like the error code translation. Peter