<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:17:30 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-1535] LustreError: 1843:0:(mds_open.c:1645:mds_close()) </title>
                <link>https://jira.whamcloud.com/browse/LU-1535</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;On the our customer lustre system, MDS thread hanged after the call traces. On MDS, the following messages showed up during the call traces.&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;Jun 17 05:45:08 ALPL505 kernel: LustreError: 1843:0:(mds_open.c:1645:mds_close()) @@@ no handle for file close ino 21989538: cookie 0x1e6d8ca7fa6bf800  req@ffff810287df6400 x1401981983149299/t0 o35-&amp;gt;c9344f7b-1e2a-0615-0b51-cbf06bb316a5@NET_0x500000a030235_UUID:0/0 lens 408/4896 e 0 to 0 dl 1339883114 ref 1 fl Interpret:/0/0 rc 0/0
Jun 17 05:45:08 ALPL505 kernel: LustreError: 1843:0:(mds_open.c:1645:mds_close()) Skipped 1 previous similar message
Jun 17 05:45:08 ALPL505 kernel: LustreError: 1843:0:(ldlm_lib.c:1919:target_send_reply_msg()) @@@ processing error (-116)  req@ffff810287df6400 x1401981983149299/t0 o35-&amp;gt;c9344f7b-1e2a-0615-0b51-cbf06bb316a5@NET_0x500000a030235_UUID:0/0 lens 408/2928 e 0 to 0 dl 1339883114 ref 1 fl Interpret:/0/0 rc -116/0
Jun 17 05:45:08 ALPL505 kernel: LustreError: 1843:0:(ldlm_lib.c:1919:target_send_reply_msg()) Skipped 1 previous similar message
Jun 17 05:45:09 ALPL505 kernel: LustreError: 2131:0:(mds_open.c:1645:mds_close()) @@@ no handle for file close ino 21922157: cookie 0x1e6d8ca7fa68693c  req@ffff810237e71c00 x1401981983149371/t0 o35-&amp;gt;c9344f7b-1e2a-0615-0b51-cbf06bb316a5@NET_0x500000a030235_UUID:0/0 lens 408/4896 e 0 to 0 dl 1339883115 ref 1 fl Interpret:/0/0 rc 0/0
Jun 17 06:02:54 ALPL505 kernel: Lustre: Service thread pid 981 was inactive for 710.00s. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="14954">LU-1535</key>
            <summary>LustreError: 1843:0:(mds_open.c:1645:mds_close()) </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="1">Fixed</resolution>
                                        <assignee username="laisiyao">Lai Siyao</assignee>
                                    <reporter username="ihara">Shuichi Ihara</reporter>
                        <labels>
                    </labels>
                <created>Sun, 17 Jun 2012 23:01:31 +0000</created>
                <updated>Fri, 22 Feb 2013 11:18:30 +0000</updated>
                            <resolved>Fri, 6 Jul 2012 13:26:46 +0000</resolved>
                                                    <fixVersion>Lustre 1.8.9</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="40720" author="ihara" created="Sun, 17 Jun 2012 23:02:44 +0000"  >&lt;p&gt;messages attached.&lt;/p&gt;</comment>
                            <comment id="40722" author="pjones" created="Mon, 18 Jun 2012 01:07:29 +0000"  >&lt;p&gt;Lai&lt;/p&gt;

&lt;p&gt;Could you please look into this one?&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="40729" author="adilger" created="Mon, 18 Jun 2012 05:25:26 +0000"  >&lt;p&gt;Ihara, what version of Lustre is this?&lt;/p&gt;</comment>
                            <comment id="40731" author="ihara" created="Mon, 18 Jun 2012 05:50:57 +0000"  >&lt;p&gt;the Lustre-1.8.6-wc1 is running on this cluster.&lt;/p&gt;</comment>
                            <comment id="40838" author="laisiyao" created="Tue, 19 Jun 2012 05:03:53 +0000"  >&lt;p&gt;This looks to be the same issue in &lt;a href=&quot;http://jira.whamcloud.com/browse/LU-1128&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;http://jira.whamcloud.com/browse/LU-1128&lt;/a&gt;. I&apos;ve backported the fix at: &lt;a href=&quot;http://review.whamcloud.com/#change,3138&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#change,3138&lt;/a&gt;. Could you find a way to verify?&lt;/p&gt;</comment>
                            <comment id="40844" author="ihara" created="Tue, 19 Jun 2012 08:39:49 +0000"  >&lt;p&gt;Lai, &lt;br/&gt;
thanks! we will try your backport patch. btw, this problem happened on MDS, does &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1128&quot; title=&quot;Complete investigation of the LDLM pool shrinker and SLV handling&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1128&quot;&gt;&lt;del&gt;LU-1128&lt;/del&gt;&lt;/a&gt; causes this problem on MDS as well?&lt;/p&gt;</comment>
                            <comment id="40846" author="laisiyao" created="Tue, 19 Jun 2012 09:21:59 +0000"  >&lt;p&gt;The issue &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1128&quot; title=&quot;Complete investigation of the LDLM pool shrinker and SLV handling&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1128&quot;&gt;&lt;del&gt;LU-1128&lt;/del&gt;&lt;/a&gt; fixed is for ldlm server, that is, it may occur on MGS, MDS and OSS.&lt;/p&gt;</comment>
                            <comment id="41554" author="laisiyao" created="Fri, 6 Jul 2012 03:58:45 +0000"  >&lt;p&gt;patched landed.&lt;/p&gt;</comment>
                            <comment id="41559" author="spitzcor" created="Fri, 6 Jul 2012 10:47:46 +0000"  >&lt;p&gt;Lai, which patch landed?  You marked this bug fixed for 2.3.0, but I don&apos;t see any master patches beyond &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1128&quot; title=&quot;Complete investigation of the LDLM pool shrinker and SLV handling&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1128&quot;&gt;&lt;del&gt;LU-1128&lt;/del&gt;&lt;/a&gt; and that was marked fixed for 2.2.0 and 2.1.2.  change #3138 landed to b1_8 so maybe this ticket should be marked fixed for 1.8.9 instead, if that is possible.&lt;/p&gt;</comment>
                            <comment id="41564" author="laisiyao" created="Fri, 6 Jul 2012 13:24:46 +0000"  >&lt;p&gt;Cory, thanks for your clarification.&lt;/p&gt;</comment>
                            <comment id="41565" author="laisiyao" created="Fri, 6 Jul 2012 13:26:46 +0000"  >&lt;p&gt;The actual fix version should be 1.8.9, if there will be one. But it&apos;s invalid to fill in that field because it doesn&apos;t exist. 1.8.8 is used.&lt;/p&gt;</comment>
                            <comment id="41582" author="pjones" created="Sun, 8 Jul 2012 02:56:36 +0000"  >&lt;p&gt;Rather than put an incorrect release we can just leave the release fixed field empty and populate it if/when we form concrete plans for a 1.8.9 release.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="11616" name="LFS05_MDS_20120617.log" size="132534" author="ihara" created="Sun, 17 Jun 2012 23:02:44 +0000"/>
                    </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|hzvgun:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>6379</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>