Have found the problem. All this was caused by missing mon_host directive in
ceph.conf. I have expected userspace to catch this, but it looks like it didn't
care.
We use DNS SRV in this cluster.
With mon_host directive reinstated, it was able to connect:
Jul 26 09:51:40 xx kernel: libceph: mon0
On Mon, Jul 26, 2021 at 5:25 PM wrote:
>
> Have found the problem. All this was caused by missing mon_host directive in
> ceph.conf. I have expected userspace to catch this, but it looks like it
> didn't care.
We should probably add an explicit check for that so that the error
message is explic
Although I appreciate the responses, they have provided zero help solving this
issue thus far.
It seems like the kernel module doesn't even get to the stage where it reads
the attributes/features of the device. It doesn't know where to connect and,
presumably, is confused by the options passed b
Hi,
> As Marc mentioned, you would need to disable unsupported features but
> you are right that the kernel doesn't make it to that point.
I remember disabling unsupported features on el7 nodes (kernel 3.10) with
Nautilus.
But the error on the map command is usually more obvious.
$ rbd feature d
On Mon, Jul 26, 2021 at 12:39 PM wrote:
>
> Although I appreciate the responses, they have provided zero help solving
> this issue thus far.
> It seems like the kernel module doesn't even get to the stage where it reads
> the attributes/features of the device. It doesn't know where to connect an
On Fri, Jul 23, 2021 at 11:58 PM wrote:
>
> Hi.
>
> I've followed the installation guide and got nautilus 14.2.22 running on el7
> via https://download.ceph.com/rpm-nautilus/el7/x86_64/ yum repo.
> I'm now trying to map a device on an el7 and getting extremely weird errors:
>
> # rbd info test1/b
EL7 client is still compatible with Nautilus
Sent from my iPhone
> On 24 Jul 2021, at 00:58, cek+c...@deepunix.net wrote:
>
> Is that because the kernel module is too old?
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email t
