On Mon, Mar 24, 2014 at 9:46 PM, Ирек Фасихов <malmyzh@xxxxxxxxx> wrote:
> Kernel module support RBD, Ilya Dryomov?
>
> Thanks?
>
>
> 2014-03-24 23:32 GMT+04:00 Michael J. Kidd <michael.kidd@xxxxxxxxxxx>:
>
>> The message 'feature set mismatch' is exactly what Gregory was talking
>> about.
>>
>> This indicates that you are using a CRUSH feature in your Ceph environment
>> that the Kernel RBD client doesn't understand. So, it's unable to
>> communicate. In this instance, it's likely to do with the cache pool
>> itself, but I'm not terribly familiar with the features support in 3.14
>> kernel...
>>
>> Thanks,
>>
>> Michael J. Kidd
>> Sr. Storage Consultant
>> Inktank Professional Services
>>
>>
>> On Mon, Mar 24, 2014 at 2:58 PM, Ирек Фасихов <malmyzh@xxxxxxxxx> wrote:
>>>
>>> Hi, Gregory!
>>> I think that there is no interesting :).
>>>
>>> dmesg:
>>> Key type dns_resolver registered
>>> Key type ceph registered
>>> libceph: loaded (mon/osd proto 15/24)
>>> rbd: loaded (major 252)
>>> libceph: mon1 192.168.100.202:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon1 192.168.100.202:6789 socket error on read
>>> libceph: mon1 192.168.100.202:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon1 192.168.100.202:6789 socket error on read
>>> libceph: mon2 192.168.100.203:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon2 192.168.100.203:6789 socket error on read
>>> libceph: mon2 192.168.100.203:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon2 192.168.100.203:6789 socket error on read
>>> libceph: mon1 192.168.100.202:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon1 192.168.100.202:6789 socket error on read
>>> libceph: mon1 192.168.100.202:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon1 192.168.100.202:6789 socket error on read
>>> libceph: mon1 192.168.100.202:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon1 192.168.100.202:6789 socket error on read
>>> libceph: mon2 192.168.100.203:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon2 192.168.100.203:6789 socket error on read
>>> libceph: mon2 192.168.100.203:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon2 192.168.100.203:6789 socket error on read
>>> libceph: mon0 192.168.100.201:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon0 192.168.100.201:6789 socket error on read
>>> libceph: mon1 192.168.100.202:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon1 192.168.100.202:6789 socket error on read
>>> libceph: mon2 192.168.100.203:6789 feature set mismatch, my 384a042a42 <
>>> server's 2384a042a42, missing 20000000000
>>> libceph: mon2 192.168.100.203:6789 socket error on read
Hi,
20000000000 is bit 41, so it's either crush tunables v3 or primary
affinity. Do you have crush chooseleaf_vary_r set to a non-default
value or primary-affinity adjusted with the 'ceph osd primary-affinity'
command?
Can you add the output of 'ceph osd dump --format=json-pretty' and the
output of 'ceph osd getcrushmap -o /tmp/crush; crushtool -d /tmp/crush'
to your Drive folder so I can check myself?
Thanks,
Ilya
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
