Re: Migration with ``drive-mirror`` + NBD will let quorum qcow2 image become larger

2020-05-20 Thread Tao Xu
On 5/19/2020 10:49 PM, Alberto Garcia wrote: On Tue 19 May 2020 11:15:44 AM CEST, Kevin Wolf wrote: But maybe it could return a limited set of flags at least so that the mirror job can get the BDRV_BLOCK_ZERO information if the quorum children agree on it. Yeah, maybe it is possible to

Re: Migration with ``drive-mirror`` + NBD will let quorum qcow2 image become larger

2020-05-19 Thread Alberto Garcia
On Tue 19 May 2020 11:15:44 AM CEST, Kevin Wolf wrote: > But maybe it could return a limited set of flags at least so that the > mirror job can get the BDRV_BLOCK_ZERO information if the quorum > children agree on it. Yeah, maybe it is possible to implement a conservative version of that function

Re: Migration with ``drive-mirror`` + NBD will let quorum qcow2 image become larger

2020-05-19 Thread Kevin Wolf
Am 19.05.2020 um 10:32 hat Tao Xu geschrieben: > Hi, > > I am using ``drive-mirror`` + NBD for live storage migration. But I find > that if I use a qcow2 image(virtual size: 10 GiB, disk size: 1.8 GiB) as a > child of quorum, then the destination image become larger(virtual size: 10 > GiB, disk

Migration with ``drive-mirror`` + NBD will let quorum qcow2 image become larger

2020-05-19 Thread Tao Xu
Hi, I am using ``drive-mirror`` + NBD for live storage migration. But I find that if I use a qcow2 image(virtual size: 10 GiB, disk size: 1.8 GiB) as a child of quorum, then the destination image become larger(virtual size: 10 GiB, disk size: 10 GiB). However if I use a qcow2 image directly,