qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre DERUMIER <aderumier@odiso.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Ceph Devel <ceph-devel@vger.kernel.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu drive-mirror to rbd storage : no sparse rbd image
Date: Mon, 13 Oct 2014 08:06:29 +0200 (CEST)	[thread overview]
Message-ID: <9fe0fedc-802d-4838-b738-c3d0932eeeda@mailpro> (raw)
In-Reply-To: <543A7BD4.4030601@redhat.com>

>>Lack of bdrv_co_write_zeroes is why detect-zeroes does not work.
>>
>>Lack of bdrv_get_block_status is why sparse->sparse does not work
>>without detect-zeroes.

Ok, thanks Paolo !

Both are missing in rbd block driver. @ceph-devel . Could it be possible to implement them ?



Also, about drive-mirror, I had tried with detect-zeroes with simple qcow2 file,
and It don't seem to help.
I'm not sure that detect-zeroes is implement in drive-mirror.

also, the target mirrored volume don't seem to have the detect-zeroes option


# info block
drive-virtio1: /source.qcow2 (qcow2)
    Detect zeroes:    on

#du -sh source.qcow2 : 2M

drive-mirror  source.qcow2 -> target.qcow2

# info block
drive-virtio1: /target.qcow2 (qcow2)

#du -sh target.qcow2 : 11G




----- Mail original -----

De: "Paolo Bonzini" <pbonzini@redhat.com>
À: "Alexandre DERUMIER" <aderumier@odiso.com>, "qemu-devel" <qemu-devel@nongnu.org>
Cc: "Ceph Devel" <ceph-devel@vger.kernel.org>
Envoyé: Dimanche 12 Octobre 2014 15:02:12
Objet: Re: qemu drive-mirror to rbd storage : no sparse rbd image

Il 08/10/2014 13:15, Alexandre DERUMIER ha scritto:
> Hi,
>
> I'm currently planning to migrate our storage to ceph/rbd through qemu drive-mirror
>
> and It seem that drive-mirror with rbd block driver, don't create a sparse image. (all zeros are copied to the target rbd).
>
> Also note, that it's working fine with "qemu-img convert" , the rbd volume is sparse after conversion.
>
>
> Could it be related to the "bdrv_co_write_zeroes" missing features in block/rbd.c ?
>
> (It's available in other block drivers (scsi,gluster,raw-aio) , and I don't have this problem with theses block drivers).

Lack of bdrv_co_write_zeroes is why detect-zeroes does not work.

Lack of bdrv_get_block_status is why sparse->sparse does not work
without detect-zeroes.

Paolo

  reply	other threads:[~2014-10-13  6:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54c55fc6-b12a-42e5-b99d-9752c8a9b19b@mailpro>
2014-10-08 11:15 ` [Qemu-devel] qemu drive-mirror to rbd storage : no sparse rbd image Alexandre DERUMIER
2014-10-11  7:01   ` Fam Zheng
2014-10-11  8:00     ` Alexandre DERUMIER
2014-10-11  8:25       ` Fam Zheng
2014-10-11  8:30         ` Andrey Korolyov
2014-10-12 10:02           ` Alexandre DERUMIER
2014-10-12 10:33         ` Alexandre DERUMIER
2014-10-12 13:02   ` Paolo Bonzini
2014-10-13  6:06     ` Alexandre DERUMIER [this message]
2014-10-13  7:06       ` Paolo Bonzini
2014-10-13  8:08         ` Alexandre DERUMIER

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=9fe0fedc-802d-4838-b738-c3d0932eeeda@mailpro \
    --to=aderumier@odiso.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).