The rbd has 2 kinds of data, metadata and data itself, the metadata gives 
information about the rbd imagen and small amounts of internal information. 
This one is place on the replicated pool and that's why it's considering that 
the image is on the replicated pool.But the actual data (big information) are 
stored in the Erasure pool.So when you start filling your image you will see 
how your replicated metadata pool grows a little bit when the actual Erasure 
data pool grows way more!
You can get information about your image using rbd info {replicated 
pool}/{image name}
-------- Mensaje original --------De: Josy <[email protected]> Fecha: 
12/10/17  8:40 PM  (GMT+01:00) Para: David Turner <[email protected]>, 
[email protected] Cc: ceph-users <[email protected]> Asunto: Re: 
[ceph-users] Erasure coding with RBD 

    Thank you for your reply.
    I created a erasure coded pool 'ecpool' and a replicated pool to
      store metadata 'ec_rep_pool'

    
     And created image as you mentioned : 

    
    rbd create --size 20G --data-pool ecpool ec_rep_pool/ectestimage1
    But the image seems to be  created in ec_rep_pool 

      
    ============

      [cephuser@ceph-las-admin-a1 ceph-cluster]$ rbd ls -l ecpool

      [cephuser@ceph-las-admin-a1 ceph-cluster]$ rbd ls -l ec_rep_pool

      NAME           SIZE
PARENT                                                                      
      FMT PROT LOCK

      ectestimage 
20480M                                                                          
     
      2

      ectestimage1
20480M                                                                          
     
      2

      

      

      Is that how it suppose to work ?
    

    On 12-10-2017 23:53, David Turner
      wrote:

    
    
      Here is your friend. 
http://docs.ceph.com/docs/luminous/rados/operations/erasure-code/#erasure-coding-with-overwrites
      

      
        On Thu, Oct 12, 2017 at 2:09 PM Jason Dillaman
          <[email protected]> wrote:

        
        The image
          metadata still needs to live in a replicated data pool --

          only the data blocks can be stored in an EC pool. Therefore,
          when

          creating the image, you should provide the "--data-pool
          <pool-name>"

          optional to specify the EC pool name.

          

          

          On Thu, Oct 12, 2017 at 2:06 PM, Josy <[email protected]>
          wrote:

          > Hi,

          >

          > I am trying to setup an erasure coded pool with rbd
          image.

          >

          > The ceph version is Luminous 12.2.1. and I understand, 
          since Luminous, RBD

          > and Cephfs can store their data in an erasure coded pool
          without use of

          > cache tiring.

          >

          > I created a pool ecpool and when trying to create a rbd
          image, gets this

          > error.

          >

          > ==============

          >

          > [cephuser@ceph-las-admin-a1 ceph-cluster]$ rbd create
          --size 20G

          > ecpool/ectestimage2

          > 2017-10-12 10:55:37.992965 7f18857fa700 -1
          librbd::image::CreateRequest:

          > 0x55608e1e0c20 handle_add_image_to_directory: error
          adding image to

          > directory: (95) Operation not supported

          > rbd: create error: (95) Operation not supported

          > ==============

          >

          >

          >

          > _______________________________________________

          > ceph-users mailing list

          > [email protected]

          > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

          

          

          

          --

          Jason

          _______________________________________________

          ceph-users mailing list

          [email protected]

          http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

        
      
    
    

  
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to