From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44260) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZpClv-0008UR-UU for qemu-devel@nongnu.org; Thu, 22 Oct 2015 06:07:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZpClq-0003r4-5F for qemu-devel@nongnu.org; Thu, 22 Oct 2015 06:06:59 -0400 Date: Thu, 22 Oct 2015 18:06:42 +0800 From: Fam Zheng Message-ID: <20151022100642.GB3850@ad.usersys.redhat.com> References: <1445501858-18790-1-git-send-email-famz@redhat.com> <56289F1C.2040605@kamp.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56289F1C.2040605@kamp.de> 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: Peter Lieven Cc: Kevin Wolf , Paolo Bonzini , qemu-block@nongnu.org, qemu-devel@nongnu.org, Ronnie Sahlberg On Thu, 10/22 10:32, Peter Lieven wrote: > 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? > It can have a backing file. Fam