On Mon, Oct 24, 2016 at 12:26 PM, Sage Weil <sweil@xxxxxxxxxx> wrote:
> Hi James,
>
> On Mon, 24 Oct 2016, LIU, Fei wrote:
>> Hi Sage,
>> We built a ceph binary package by ourselves based on Jewel 10.2.2 source
>> code in Alibaba. However,
>> we got below error with krbd/libceph during rbd map with CentOS
>> 7.2(Kernel 3.10). I am still able to use rados put/fio rbd to put key
>> value pairs into the ceph cluster. So , we are kind of confidence that was
>> krbd issues.
>>
>> We do disable sign message.
>>
>> cephx_sign_messages = false
>>
>> cephx_require_signatures = false
>>
>>
>> And also we make sure we have latest
>> struct ceph_msg_header {
>> __le64 seq; /* message seq# for this session */
>> __le64 tid; /* transaction id */
>> __le16 type; /* message type */
>> __le16 priority; /* priority. higher value == higher priority */
>> __le16 version; /* version of message encoding */
>>
>> __le32 front_len; /* bytes in main payload */
>> __le32 middle_len;/* bytes in middle payload */
>> __le32 data_len; /* bytes of data payload */
>> __le16 data_off; /* sender: include full offset;
>> receiver: mask against ~PAGE_MASK */
>>
>> struct ceph_entity_name src;
>> __le16 compat_version;
>> __le16 reserved;
>> __le32 crc; /* header crc32c */
>> } __attribute__ ((packed));
>>
>> Any help would be appreciated greatly.
>>
>> Regards,
>> James
>>
>>
>> [69318.023791] libceph: read_partial_message ffff881fc6140000 signature
>> check failed
>>
>> [69318.031451] libceph: osd6 11.238.201.173:6824 bad crc
>
> This doesn't sound familiar. Ilya, have you seen anything like this
> with the centos 7.2 kernel client?
>
> Perhaps you've made some changes from the upstream ceph code and that is
> part of the problem?
Hi James,
"rbd map" doesn't generally parse ceph.conf. In this case you need to
map with -o nocephx_sign_messages or add it to rbd_default_map_options
config variable, which is a comma-separated list of default map options.
Thanks,
Ilya
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
