Hi experts,
I didn’t find any answers here or on global web search.
I’ve updated 15.5 from 5.14.21-150500.55.44-default to 5.14.21-150500.55.83-default and started to get this syslog notification : nfsd: inode locked twice during operation
Does anybody saw it and knows where it comes from and how to solve it.
Thank you.
By “15.5” do you mean openSUSE Leap 15.5 or SUSE Linux Enterprise Server 15 SP5?
I’ve found https://lore.kernel.org/all/CAKAoaQ=CaBGSnoTK9GteCj=CWjMxiGcEhozCOuqu7-ygBeAHYQ@mail.gmail.com/T/ which suggests an update to nfsd so I’d at least test this against SLES15 SP6 with a view to updating and upgrading your server.
Thank you for your replay,
I have SUSE Linux Enterprise Server 15 SP5
In terms of SLES distributions, I believe these messages are unique to 15 SP5. They first appeared in kernel 5.14.21-150500.55.73.1. Work to address them is only being released in the 15 SP5 LTSS channel. (General support for 15 SP5 ended as of Dec 31, 2024.) In reviewing internal reports and work on this issue, it seems that there is not a known functional failure connected with these messages. Even so, I’m not absolutely sure the absense of functional issues can be guaranteed – there may be unknown variations that can exist in fringe conditions. To SUSE’s knowledge, they are merely unnecessary, annoying warnings and we are eliminating them. There is indication from one customer that higher CPU and memory usage may have been present along with them. That may be normal considering the extra and constant logging of messages that is taking place. But this symptom has not been directly confirmed. LTSS maintenance kernel 5.14.21-150500-55.91 (released Jan 21 2025) and later eliminate these messages from some code paths that can generate them. There was an additional code path identified more recently, which some workloads run into and some do not. A fix for that has been made but at the moment is only available in PTF form from SUSE’s Tech Support organization. I would guess it might arrive in LTSS maintenance in mid March.
Newer kernel 5.14.21-150500-55.97 contains the additional fix (which, in my last comment, I said would be coming).