Re: Bad CRC in data messages logging out to syslog

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le lundi 25 avril 2022, 17:46:04 CEST Chris Page a ?crit :
> Hi,
> 
> Every now and then I am getting the following logs -
> 
> pve01 2022-04-25T16:41:03.109+0100 7ff35b6da700  0 bad crc in data
> 3860390385 != exp 919468086 from v1:10.0.0.111:0/873787122
> pve01 2022-04-25T16:41:04.361+0100 7fb0e2feb700  0 bad crc in data
> 1141834112 != exp 797386370 from v1:10.0.0.111:0/873787122
> pve03 2022-04-25T16:42:03.988+0100 7ffbb02d1700  0 bad crc in data
> 2357454667 != exp 1757772123 from v1:10.0.0.111:0/873787122
> pve01 2022-04-25T16:42:04.394+0100 7faf49cad700  0 bad crc in data
> 329941200 != exp 2275667382 from v1:10.0.0.111:0/873787122
> 
> The messages look fairly consistent and all come in at a similar time
> across nodes. Is this anything to worry about? Ceph doesn't seem to be
> highlighting any consistency issues and has no problems performing scrubs.
> 
> Chris.


Hello Chris,

You can look at my thread, with the title "OSD crash with end_of_buffer + bad 
crc".

On my side, I resolved it by changing a network card.




_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux