<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:43:53 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-4567] NFS exports - The mds_getattr operation failed with -43</title>
                <link>https://jira.whamcloud.com/browse/LU-4567</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;We are seeing a lot of &quot;timeouts&quot; to the MDS on two round-robin clients/NFS exporters. The issue seems to be unique to going via NFS. I am aware that the &quot;-43&quot; error is related to UID/GID mismatches but I am almost certain that these are correctly configured to be the same everywhere. Even still should the Lustre client essentially disconnect and then return IO errors to the NFS clients for a short period of time if it can&apos;t match a UID/GID?&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;Jan 24 01:36:26 lustre1 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr_lock operation failed with -43
Jan 24 01:36:26 lustre1 kernel: LustreError: Skipped 527 previous similar messages
Jan 24 01:36:26 lustre1 kernel: LustreError: 3174:0:(llite_nfs.c:276:ll_get_parent()) failure -43 inode 2524321369 get parent
Jan 24 01:36:26 lustre1 kernel: LustreError: 3174:0:(llite_nfs.c:276:ll_get_parent()) Skipped 58 previous similar messages
Jan 24 01:36:26 lustre1 kernel: nfsd: non-standard errno: -43

Jan 24 01:36:26 mds kernel: LustreError: 5942:0:(ldlm_lib.c:1921:target_send_reply_msg()) @@@ processing error (-43)  req@ffff8104ce78b000 x1447826783625469/t0 o34-&amp;gt;73d957f1-091b-9ffc-a5db-3402eba274ff@NET_0x200000a151615_UUID:0/0 lens 424/192 e 0 to 0 dl 1390527406 ref 1 fl Interpret:/0/0 rc -43/0
Jan 24 01:36:26 mds kernel: LustreError: 5942:0:(ldlm_lib.c:1921:target_send_reply_msg()) Skipped 319 previous similar messages
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;They occur at reasonably regular periods because we have an application that scans various directories every 5 mins over NFS. Looking at the occurrences across both Lustre clients/NFS exporters:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
lustre1 /root # tail -f /&lt;span class=&quot;code-keyword&quot;&gt;var&lt;/span&gt;/log/messages | grep &lt;span class=&quot;code-quote&quot;&gt;&quot;10.21.22.10&quot;&lt;/span&gt;
Jan 30 12:01:01 lustre1 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr_lock operation failed with -43
Jan 30 12:06:01 lustre1 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr_lock operation failed with -43
Jan 30 12:11:00 lustre1 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr_lock operation failed with -43
Jan 30 12:16:02 lustre1 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr_lock operation failed with -43
Jan 30 12:21:01 lustre1 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr_lock operation failed with -43
Jan 30 12:31:32 lustre1 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr_lock operation failed with -43
Jan 30 12:51:14 lustre1 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr_lock operation failed with -43
Jan 30 12:56:13 lustre1 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr_lock operation failed with -43

lustre2 /root # tail -f /&lt;span class=&quot;code-keyword&quot;&gt;var&lt;/span&gt;/log/messages | grep &lt;span class=&quot;code-quote&quot;&gt;&quot;10.21.22.10&quot;&lt;/span&gt;
Jan 30 12:01:06 lustre2 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr operation failed with -43
Jan 30 12:01:06 lustre2 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr operation failed with -43
Jan 30 12:01:07 lustre2 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr operation failed with -43
Jan 30 12:01:08 lustre2 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr operation failed with -43
Jan 30 12:01:26 lustre2 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr operation failed with -43
Jan 30 12:11:25 lustre2 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr operation failed with -43
Jan 30 12:11:42 lustre2 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr operation failed with -43
Jan 30 12:21:01 lustre2 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr operation failed with -43
Jan 30 12:21:52 lustre2 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr operation failed with -43
Jan 30 12:37:03 lustre2 kernel: LustreError: 11-0: an error occurred &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; communicating with 10.21.22.10@tcp. The mds_getattr operation failed with -43
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Am am reasonably sure that both the network layer and UID/GIDs are fine.&lt;/p&gt;

&lt;p&gt;Regards,&lt;/p&gt;

&lt;p&gt;Daire&lt;/p&gt;</description>
                <environment></environment>
        <key id="22931">LU-4567</key>
            <summary>NFS exports - The mds_getattr operation failed with -43</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="pjones">Peter Jones</assignee>
                                    <reporter username="daire">Daire Byrne</reporter>
                        <labels>
                    </labels>
                <created>Thu, 30 Jan 2014 13:13:42 +0000</created>
                <updated>Wed, 2 Apr 2014 02:52:04 +0000</updated>
                            <resolved>Wed, 2 Apr 2014 02:52:04 +0000</resolved>
                                    <version>Lustre 1.8.9</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="80801" author="daire" created="Wed, 2 Apr 2014 02:07:52 +0000"  >&lt;p&gt;Well we are not seeing this on our 2.4 cluster so I guess we don&apos;t care so much anymore. We will stop using the v1.8 cluster to serve data over NFS.&lt;/p&gt;</comment>
                            <comment id="80804" author="pjones" created="Wed, 2 Apr 2014 02:52:04 +0000"  >&lt;p&gt;ok - thanks Daire!&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzwdwn:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>12462</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>