Yes, I just verified it again. Can create the rbd image with data-pool (EC pool), but cannot access it with disable command.
ems@rack9-ems-5:~/ec-rbd/master/ceph/build$ ceph -s
cluster f791d144-c685-4e5c-bbff-d569930befc4
health HEALTH_OK
monmap e2: 1 mons at {a=127.0.0.1:40000/0}
election epoch 8, quorum 0 a
mgr no daemons active
osdmap e62: 5 osds: 5 up, 5 in
flags sortbitwise,require_jewel_osds,require_kraken_osds
pgmap v37903: 56 pgs, 5 pools, 187 MB data, 90 objects
449 GB used, 381 GB / 830 GB avail
56 active+clean
2016-12-08 07:27:06.417479 7f31ad9dc700 0 lockdep stop
ems@rack9-ems-5:~/ec-rbd/master/ceph/build$
ems@rack9-ems-5:~/ec-rbd/master/ceph/build$ ./bin/rbd create rbdimg_EC4 --size 1024 --data-pool aravecpool32
ems@rack9-ems-5:~/ec-rbd/master/ceph/build$
ems@rack9-ems-5:~/ec-rbd/master/ceph/build$
ems@rack9-ems-5:~/ec-rbd/master/ceph/build$ rbd ls
rbdimg_EC1
rbdimg_EC2
rbdimg_EC3
rbdimg_EC4
ems@rack9-ems-5:~/ec-rbd/master/ceph/build$ sudo rbd map rbdimg_EC4
[sudo] password for ems:
rbd: sysfs write failed
rbd: map failed: (6) No such device or address
ems@rack9-ems-5:~/ec-rbd/master/ceph/build$
ems@rack9-ems-5:~/ec-rbd/master/ceph/build$ sudo rbd feature disable rbdimg_EC2 deep-flatten fast-diff
ems@rack9-ems-5:~/ec-rbd/master/ceph/build$ sudo rbd feature disable rbdimg_EC4 exclusive-lock deep-flatten fast-diff object-map
[sudo] password for ems:
2016-12-08 07:26:07.043474 7feae37fe700 -1 librbd::image::RefreshRequest: Image uses unsupported features: 128
2016-12-08 07:26:07.043572 7feae2ffd700 -1 librbd::image::OpenRequest: failed to refresh image: (38) Function not implemented
2016-12-08 07:26:07.084825 7feae2ffd700 -1 librbd::ImageState: failed to open image: (38) Function not implemented
rbd: error opening image rbdimg_EC4: (38) Function not implemented
ems@rack9-ems-5:~/ec-rbd/master/ceph/build$
Is there any experimental flag that needs to be added in ceph.conf?
Aravind
-----Original Message-----
From: Jason Dillaman [mailto:jdillama@xxxxxxxxxx]
Sent: Thursday, December 08, 2016 2:05 AM
To: Aravind Ramesh <Aravind.Ramesh@xxxxxxxxxxx>
Cc: ceph-users@xxxxxxxxxxxxxx
Subject: Re: RBD: Failed to map rbd device with data pool enabled.
I cannot recreate that "rbd feature disable" error using a master branch build from yesterday. Can you still reproduce this where your rbd CLI can create a data pool image but cannot access the image afterwards?
As for how to run against a librbd-backed client, it depends on what your end goal is. QEMU and fio are just two examples of applications that directly utilize librbd.
PLEASE NOTE: The information contained in this electronic mail message is intended only for the use of the designated recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender by telephone or e-mail (as shown above) immediately and destroy any and all copies of this message in your possession (whether hard copies or electronically stored copies).
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
