Qcow2 and RBD Import

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

Going through the documentation I am aware that I should be using RAW images instead of Qcow2 when storing my images in ceph.

I have carried a small test to understand how this is going.

[root@ ~]# qemu-img create -f qcow2 test.qcow2 100G
Formatting 'test.qcow2', fmt=qcow2 size=107374182400 encryption=off cluster_size=65536 lazy_refcounts=off
[root@ ~]# qemu-img info test.qcow2
image: test.qcow2
file format: qcow2
virtual size: 100G (107374182400 bytes)
disk size: 196K
cluster_size: 65536
Format specific information:
    compat: 1.1
    lazy refcounts: false


After that i havce imported the image to my ceph cluster:

[root@ ~]# rbd import test.qcow2 --pool openstack_images
rbd: --pool is deprecated for import, use --dest-pool
Importing image: 100% complete...done.


Now, watching the size of the image and it's information :

[root@ ~]# rbd info openstack_images/test.qcow2
rbd image 'test.qcow2':
        size 194 kB in 1 objects
        order 22 (4096 kB objects)
        block_name_prefix: rbd_data.123ca2ae8944a
        format: 2
        features: layering, exclusive-lock, object-map, fast-diff, deep-flatten
        flags:

So, what does this exactly mean ? am i able to store qcow2 ? Is it safe to store qcow2? in the backend, how did that happen , were the image converted somehow to raw ? have the other part of the image that did not have any information stored trimmed ?

Thank you 
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux