All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@suse.de>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] ioemu block device extent checks
Date: Tue, 04 Mar 2008 11:16:28 +0100	[thread overview]
Message-ID: <47CD217C.6010902@suse.de> (raw)
In-Reply-To: <20080226204130.GC24548@redhat.com>

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

  parent reply	other threads:[~2008-03-04 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 16:38 [PATCH] ioemu block device extent checks Ian Jackson
2008-02-26 20:41 ` Daniel P. Berrange
2008-02-27 11:28   ` Ian Jackson
2008-02-27 12:57     ` Daniel P. Berrange
2008-02-27 13:14       ` Ian Jackson
2008-02-27 13:21         ` Daniel P. Berrange
2008-03-04 10:16   ` Kevin Wolf [this message]
2008-03-04 10:08     ` Keir Fraser
2008-03-04 11:05       ` Kevin Wolf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47CD217C.6010902@suse.de \
    --to=kwolf@suse.de \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=berrange@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.