On Mon, Jun 30, 2014 at 05:40:16PM -0600, Eric Blake wrote:
> On 06/30/2014 05:16 PM, Eric Blake wrote:
> > I'm trying to track down a core dump with the QMP drive-mirror command.
>
> Looks like the bug is related to a base image that is not a multiple of
> a cluster size.
>
> >
> > # in one ter
On 06/30/2014 05:16 PM, Eric Blake wrote:
> I'm trying to track down a core dump with the QMP drive-mirror command.
Looks like the bug is related to a base image that is not a multiple of
a cluster size.
>
> # in one terminal:
> cd /tmp
> rm -f base.img snap1.img snap2.img copy.img
>
> # base.i
On 06/30/2014 05:16 PM, Eric Blake wrote:
> I'm trying to track down a core dump with the QMP drive-mirror command.
Oh, and a followup question:
I discovered that if I try to use drive-mirror to a file that is not
already large enough, the job starts successfully but fails at the point
where it e
I'm trying to track down a core dump with the QMP drive-mirror command.
# in one terminal:
cd /tmp
rm -f base.img snap1.img snap2.img copy.img
# base.img <- snap1.img <- snap2.img; intentionally populating base.img
# with a qcow2 header, but treating it as raw data
qemu-img create -f qcow2 base.i
