From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kevin Wolf <kwolf@suse.de>
Subject: Re: [PATCH] ioemu block device extent checks
Date: Tue, 04 Mar 2008 11:16:28 +0100
Message-ID: <47CD217C.6010902@suse.de>
References: <18363.1536.661607.292188@mariner.uk.xensource.com>
	<20080226204130.GC24548@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20080226204130.GC24548@redhat.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

Daniel P. Berrange schrieb:
> FYI, this patch causes massive unrecoverable data loss / corruption on
> QCow2 files. The checks themselves are OK in terms of the first level
> of bdrv_* calls from the guest. The qcow driver though calls back into
> the raw driver for performing I/O on its underlying file. The qcow 
> driver relies on this file being grow-on-demand for purposes of allocating
> new qcow sectors. The safety checks cause this allocation to fail and
> it all goes downhill from there :-(  

I just hit this problem. What's the status?  If I understand correctly,
you discussed two different solutions and as a result no fix at all got
committed.

Kevin