https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-11123 Lustre <p>Hello,</p> <p>Today our users started to report intermittent file access issues on Oak. I noticed the following messages on one client (2.10.4):</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> Jul 05 14:32:21 sh-ln01.stanford.edu kernel: LustreError: 155141:0:(xattr.c:377:ll_xattr_list()) server bug: replied size 236 &gt; 132 Jul 05 14:32:41 sh-ln01.stanford.edu kernel: LustreError: 171588:0:(xattr.c:377:ll_xattr_list()) server bug: replied size 164 &gt; 132 Jul 05 14:32:41 sh-ln01.stanford.edu kernel: LustreError: 171588:0:(xattr.c:377:ll_xattr_list()) Skipped 5 previous similar messages Jul 05 14:32:47 sh-ln01.stanford.edu kernel: LustreError: 176583:0:(xattr.c:377:ll_xattr_list()) server bug: replied size 172 &gt; 132 Jul 05 14:32:47 sh-ln01.stanford.edu kernel: LustreError: 176583:0:(xattr.c:377:ll_xattr_list()) Skipped 59 previous similar messages Jul 05 14:33:23 sh-ln01.stanford.edu kernel: LustreError: 10776:0:(xattr.c:377:ll_xattr_list()) server bug: replied size 172 &gt; 132 Jul 05 14:33:23 sh-ln01.stanford.edu kernel: LustreError: 10776:0:(xattr.c:377:ll_xattr_list()) Skipped 58 previous similar messages </pre> </div></div> <p>These errors messages are the only Lustre Error I can see on this impacted client, however they are not very helpful as I'm not even sure it happened on Oak or another Lustre filesystem...</p> <p>The impacted directories are using ACLs but only a very few, less than 10. We have other directories with &gt;32 ACLs and haven't seen this issue.</p> <p>The issue doesn't seem to be easily reproducible neither. I'm still investigating.</p> <p>If you have any ideas on how to troubleshoot this, please let me know.</p> <p>Thanks!<br/> Stephane</p> <p> </p> <p> </p> clients: 2.10.4 clients, servers: 2.10.3 + <a href="https://jira.whamcloud.com/browse/LU-10783" title="kernel update [RHEL7.4 3.10.0-693.21.1.el7]" class="issue-link" data-issue-key="LU-10783"><strike>LU-10783</strike></a> (kernel update RHEL7.4) LU-11123

LustreError in ll_xattr_list() server bug: replied size 236 > 132

Bug Major Resolved Cannot Reproduce John Hammond Stephane Thiell Thu, 5 Jul 2018 21:56:06 +0000 Sun, 29 Jul 2018 05:13:48 +0000 Sun, 29 Jul 2018 05:11:12 +0000 Lustre 2.10.3 Lustre 2.10.4 0 3 <p>NOTE: I'm not actually sure I need to post here for our former Intel Oak support, please advise.</p> <p>But... After further investigations, it seems that these messages could be a side effect of a known limitation of nodemapping/Lustre permissions/caching, but not the root cause of our issue, which has been identified.</p> <p>It would be nice to definitively fix the client inode cache on Lustre to avoid confusion, as already explained in <a href="https://jira.whamcloud.com/browse/LU-10884" title="stat() on lustre mount point / limited client trust in l_getidentity" class="issue-link" data-issue-key="LU-10884">LU-10884</a>.</p> <p>John</p> <p>Can you please advise?</p> <p>Thanks</p> <p>Peter</p> <p>Hi Stephane,</p> <p>Could you give any more detail about the file access issues? Is there any Samba or NFS export involved on this node? Some thoughts:</p> <p>This error message cannot be reached for the "system.posix_acl_access" xattr but it can be for the "system.posix_acl_default" and the expected and returned value sizes look right for that xattr. It's not clear who or what is asking for "system.posix_acl_default" since this xattr is really used on the server. Note that this message is easy to produce by creating a directory with enough default ACLs and then using setfacl or getfacl on it.</p> <p>The message is a bit misleading since the server does not actually consider the size of the client size buffer. Instead it just creates the reply with a large enough buffer and sends the value back. And the client side getxattr code is actually handing this correctly by returning <tt>-ERANGE</tt>.</p> <p>The change <a href="https://review.whamcloud.com/#/c/32739/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/#/c/32739/</a> (<a href="https://jira.whamcloud.com/browse/LU-11074" title="Invalid argument reading file caps" class="issue-link" data-issue-key="LU-11074"><del>LU-11074</del></a> mdc: set correct body eadatasize for getxattr()) may help you avoid this situation. Would you be willing to try it?</p> <p>Hi John,<br/> Thanks for your reply and detailed explanation (and sorry for the delay, all notification emails from whamcloud.com got into my Clutter mailbox...).<br/> This was on a Sherlock login node, so no SMB/NFS export involved there. We haven't seen the problem again so I don't think it's worth patching just for that at this point.</p> <p>ok Stephane. Meanwhile the fix is queued up for a future LTS release so hopefully you'll get it in due course anyway.</p> <p>Awesome, thanks Peter.</p> Related LU-11074 Development Rank 1|hzzyt3: Rank (Obsolete) 9223372036854775807 Severity