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 by userspace. Obviously, I have already tried "--user", "--name" and so on with similar messages in dmesg. I don't feel like downgrading to 10. Any way to make el7 work with 14 userspace utils? I have also just realized there was 1 message missing from provided logs, which somehow was logged by userspace(?) and not kernel. Here's the full log: # rbd device map test1/blk1 --user testing-rw Jul 26 05:33:53 xx key.dns_resolver[9147]: name=testing-rw: No address associated with name Jul 26 05:33:53 xx kernel: libceph: resolve 'name=testing-rw' (ret=-3): failed Jul 26 05:33:53 xx kernel: libceph: parse_ips bad ip 'name=testing-rw,key=client.testing-rw' # rbd info test1/blk1 --user testing-rw works perfectly Thanks. On 7/24/21 12:47 PM, Marc wrote: > > If you have the default kernel you can not use all these features. I think even dmesg shows you something about that when mapping. > > >> -----Original Message----- >> From: cek+ceph@xxxxxxxxxxxx >> Sent: Friday, 23 July 2021 23:58 >> To: ceph-users@xxxxxxx >> Subject: *****SPAM***** unable to map device with krbd on >> el7 with ceph nautilus >> >> Hi. >> >> I've followed the installation guide and got nautilus 14.2.22 running on _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |