On Jan 3, 2025, at 03:03, Peter Grandi <p...@lustre.list.sabi.co.uk> wrote:
[...] If this is a manifestation of LU-16637 there is a fix, but I have checked the changelogs and LU-16637 is listed as applied to 2.16.0 but it does not seem to be listed in the 2.15.[1-6] changelogs. This is indeed this bug, and as the ticket said, this is not fixed in 2.15.x, only 2.16.0 I've no idea if this will ever make 2.15.x You can always take the patch and apply it locally to your clients to see if it fixes the issue. I was wondering whether to try that, but that the fix had not already been applied to 2.16 got me to think that there were some subtle changes between 2.15 and 2.16 that made it a difficult operation. But I will try. There are only so many hours in a day, and we don't port every patch back to b2_15. BTW I can easily switch to 2.16 except that I cannot yet easily switch away from EL8, and allegedly 2.16 is not available for EL8, at least in pre-compiled form: https://downloads.whamcloud.com/public/lustre/lustre-2.16.1/ I can easily rebuild from sources, but I wonder whether there is some specific incompatibility between 2.16 and the EL8 kernel and libraries... The 2.16 code was tested with el8 on a regular basis, but the primary distro that it is intended to work with is el9.x. Cheers, Andreas — Andreas Dilger Lustre Principal Architect Whamcloud/DDN
_______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
