WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] ioemu block device extent checks

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] ioemu block device extent checks
From: Kevin Wolf <kwolf@xxxxxxx>
Date: Tue, 04 Mar 2008 11:16:28 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Tue, 04 Mar 2008 02:05:11 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080226204130.GC24548@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <18363.1536.661607.292188@xxxxxxxxxxxxxxxxxxxxxxxx> <20080226204130.GC24548@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.8 (X11/20060911)
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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>