The kernel client does not yet support the new RBD features of exclusive-lock, object-map, etc. Work is currently in-progress to add this support in the future. In the meantime, if you require something similar, you can script your mount commands around the existing RBD advisory locking approach via "rbd lock add/remove" to verify that no other client has the image mounted before attempting to mount it locally. -- Jason Dillaman ----- Original Message ----- > From: "Allen Liao" <aliao.svsgames@xxxxxxxxx> > To: ceph-users@xxxxxxxxxxxxxx > Sent: Wednesday, September 23, 2015 6:10:41 PM > Subject: rbd map failing for image with exclusive-lock feature > Hi all, > I'm unable to map a block device for an image that was created with > exclusive-lock feature: > $ sudo rbd create foo --size 4096 --image-features=4 --image-format=2 > $ sudo rbd map foo > rbd: sysfs write failed > rbd: map failed: (6) No such device or address > How do I map the image? I've tried locking an image before mapping it but I > get the same result. If I omit the "--image-features=4" when creating the > image then I can map it just fine. > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |