Closed teralype closed 2 years ago
Hi,
You are right, by default driver doesn't set the features of the image, you have to set your default image features by default on the ceph.conf.
When using the KernelRBD (krbd) mount client, it doesn't have support for several options, so the correct way to deal with it is just like you have done it.
@teralype still have this problem? I just bumped into it... :(
Hi @r3pek,
You have to default the image features in the cluster by default, due the kernel mounter doesn't support the features that CEPH set by defualt for the images.
You need add this lines to all you ceph.conf config files, normally placed at /etc/ceph/Ceph.conf [global] rbd_default_features = 3
Option2: You have the option to not default the features in the CEPH, and create every image manually with the features you want, unsing the CLI client, but i don't recommend it.
More info: http://docs.ceph.com/docs/jewel/man/8/rbd/
Regards.
@box-daxter i created the images manually (using the dashboard) so it was not a features problem because the kernel could mount the images just fine.
Ok, assuming your rbd info looks like:
root@jump1:~# rbd info ssd/xxxxxxxxxxxxxxxxxxx
rbd image 'xxxxxxxxxxxxxxxxxxx':
size 40GiB in 10240 objects
order 22 (4MiB objects)
block_name_prefix: rbd_data.231638433f680b
format: 2
features: layering, striping
flags:
create_timestamp: Tue Jan 12 19:42:07 2019
stripe unit: 4MiB
stripe count: 1
Then the issue, is in the rbd plugin installation. It's a little tricky. Drain the node and reinstall the whole driver.
Ensure you can manually mount the rbd image from bash in the faulty node.
features: layering, exclusive-lock
and i did drain the node several times... :( (mount still works on host)
I'm not 100% sure, but if don't remember bad, exclusive-lock was not supported by the kernel today.
Not sure what ceph version you are on, but I was having the unable to mount exit 1 error on nautilus. This[1] fork adds support to nautilus which fixed the issue for me.
New driver release 3.0.0 with Nautilus support thanks to @diurnalist
Following the instructions on the README.md:
I figured out that I need to add the following to the
global
section in/etc/ceph/ceph.conf
Then, after restarting Docker, it works:
However, I can't start a Docker container using this volume:
This happens in both Ubuntu 14.04 and Ubuntu 16.04 using Ceph 10.2.11. Any ideas?