Hey Li, thank you for the quick reply. So the kernel on the cluster nodes might be the issue here? I thought the client kernel is the only relevant one (since we cephadm). Anyhow, we plan to upgrade the cluster nodes to Rocky 8 soon. We'll see if this helps with the issue. Best, Mathias On 2/21/2023 1:00 AM, Xiubo Li wrote: > > On 20/02/2023 22:28, Kuhring, Mathias wrote: >> Hey Dan, hey Ilya >> >> I know this issue is two years old already, but we are having similar >> issues. >> >> Do you know, if the fixes got ever backported to RHEL kernels? > > It's already backported to RHEL 8 long time ago since > kernel-4.18.0-154.el8. > >> Not looking for el7 but rather el8 fixes. >> Wondering if the patches were backported and we shouldn't actually see >> these issues. >> Or if you could maybe resolve them with a kernel upgrade. >> >> Most active clients are currently on kernel versions such as: >> 4.18.0-348.el8.0.2.x86_64, 4.18.0-348.2.1.el8_5.x86_64, >> 4.18.0-348.7.1.el8_5.x86_64 >> >> While the cluster runs with kernel 3.10.0-1160.42.2.el7.x86_64 and >> cephadm with >> ceph version 17.2.1 (ec95624474b1871a821a912b8c3af68f8f8e7aa1) quincy >> (stable). > > It seems not backported to el7 yet. > > Thanks, > >> Not sure, if the cluster kernel is actually relevant here for OSD <> >> kernel client connection. >> >> Thanks you for your help. >> >> Best, Mathias >> >> _______________________________________________ >> ceph-users mailing list -- ceph-users@xxxxxxx >> To unsubscribe send an email to ceph-users-leave@xxxxxxx >> > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |