<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:43:09 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-4485]  Some error message on lustre client</title>
                <link>https://jira.whamcloud.com/browse/LU-4485</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;On a client we have an initial problem with quota &quot;kernel: LustreError: 11-0: an error occurred while communicating with 10.121.13.59@tcp. The ost_write operation failed with -122&quot; , after we have some error message of which we do not understand the meaning. Do you have any suggestions?&lt;/p&gt;

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

&lt;p&gt;Augusto Casciola&lt;/p&gt;</description>
                <environment>operating system redhat 5.7&lt;br/&gt;
lustre  1.8.7</environment>
        <key id="22734">LU-4485</key>
            <summary> Some error message on lustre client</summary>
                <type id="3" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11318&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</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="6">Not a Bug</resolution>
                                        <assignee username="niu">Niu Yawei</assignee>
                                    <reporter username="lustre.support">Supporto Lustre Jnet2000</reporter>
                        <labels>
                    </labels>
                <created>Tue, 14 Jan 2014 14:35:09 +0000</created>
                <updated>Thu, 27 Feb 2014 18:47:33 +0000</updated>
                            <resolved>Thu, 27 Feb 2014 18:47:33 +0000</resolved>
                                    <version>Lustre 1.8.7</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="74927" author="pjones" created="Tue, 14 Jan 2014 14:43:34 +0000"  >&lt;p&gt;Niu&lt;/p&gt;

&lt;p&gt;Could you please advise with this ticket?&lt;/p&gt;

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

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="74931" author="niu" created="Tue, 14 Jan 2014 14:53:31 +0000"  >&lt;p&gt;The messages means &quot;write failed with EDQUOT (run out of quota)&quot;, looks some user is over quota.&lt;/p&gt;</comment>
                            <comment id="74933" author="niu" created="Tue, 14 Jan 2014 15:00:28 +0000"  >&lt;p&gt;You can use &quot;lfs quota -u uid/gid -v fsname&quot; to check the quota limit and usage for the user, if it&apos;s not over quota, could you upload the syslog on OSS (10.121.13.59@tcp) to see why it returned EDQUOT?&lt;/p&gt;</comment>
                            <comment id="74934" author="lustre.support" created="Tue, 14 Jan 2014 15:01:55 +0000"  >&lt;p&gt;In the attachment file we have these errors after the error of quota. Refer to the quota ?&lt;/p&gt;



&lt;p&gt;&quot;2014-01-07T17:11:40.337576+01:00 osiride-lp-041 kernel: Lustre: 23101:0:(client.c:1487:ptlrpc_expire_one_request()) @@@ Request x1436582400258712 sent from home-OST0008-osc-ffff81063fc2f800 to NID 10.121.13.28@tcp 7s ago has timed out (7s prior to deadline).&lt;br/&gt;
2014-01-07T17:11:40.337583+01:00 osiride-lp-041 kernel:  req@ffff810806324c00 x1436582400258712/t0 o103-&amp;gt;home-OST0008_UUID@10.121.13.28@tcp:17/18 lens 312/384 e 0 to 1 dl 1389111100 ref 2 fl Rpc:N/0/0 rc 0/0&lt;br/&gt;
2014-01-07T17:11:40.337589+01:00 osiride-lp-041 kernel: Lustre: home-OST0008-osc-ffff81063fc2f800: Connection to service home-OST0008 via nid 10.121.13.28@tcp was lost; in progress operations using this service will wait for recovery to complete.&lt;br/&gt;
2014-01-07T17:11:40.337595+01:00 osiride-lp-041 kernel: LustreError: 23101:0:(ldlm_request.c:1039:ldlm_cli_cancel_req()) Got rc -11 from cancel RPC: canceling anyway&lt;br/&gt;
2014-01-07T17:11:40.337601+01:00 osiride-lp-041 kernel: LustreError: 23101:0:(ldlm_request.c:1597:ldlm_cli_cancel_list()) ldlm_cli_cancel_list: -11&lt;br/&gt;
2014-01-07T17:11:40.866529+01:00 osiride-lp-041 kernel: Lustre: 7801:0:(client.c:1487:ptlrpc_expire_one_request()) @@@ Request x1436582400258725 sent from home-OST0008-osc-ffff81063fc2f800 to NID 10.121.13.28@tcp 7s ago has timed out (7s prior to deadline).&lt;br/&gt;
2014-01-07T17:11:40.866542+01:00 osiride-lp-041 kernel:  req@ffff8107ddac0800 x1436582400258725/t0 o13-&amp;gt;home-OST0008_UUID@10.121.13.28@tcp:7/4 lens 192/528 e 0 to 1 dl 1389111100 ref 2 fl Rpc:/0/0 rc 0/0&lt;br/&gt;
2014-01-07T17:11:41.263604+01:00 osiride-lp-041 kernel: Lustre: home-OST000b-osc-ffff81063fc2f800: Connection to service home-OST000b via nid 10.121.13.28@tcp was lost; in progress operations using this service will wait for recovery to complete.&lt;br/&gt;
2014-01-07T17:11:41.263618+01:00 osiride-lp-041 kernel: failure to allocate a tage (491)&lt;br/&gt;
2014-01-07T17:11:41.263624+01:00 osiride-lp-041 kernel: LustreError: 7780:0:(ldlm_request.c:1039:ldlm_cli_cancel_req()) Got rc -11 from cancel RPC: canceling anyway&lt;br/&gt;
2014-01-07T17:11:41.263628+01:00 osiride-lp-041 kernel: LustreError: 7780:0:(ldlm_request.c:1597:ldlm_cli_cancel_list()) ldlm_cli_cancel_list: -11&lt;br/&gt;
2014-01-07T17:11:41.566994+01:00 osiride-lp-041 kernel: Lustre: 23093:0:(client.c:1487:ptlrpc_expire_one_request()) @@@ Request x1436582400258713 sent from home-OST0007-osc-ffff81063fc2f800 to NID 10.121.13.28@tcp 8s ago has timed out (8s prior to deadline).&lt;br/&gt;
2014-01-07T17:11:41.567020+01:00 osiride-lp-041 kernel:  req@ffff8109d781c400 x1436582400258713/t0 o103-&amp;gt;home-OST0007_UUID@10.121.13.28@tcp:17/18 lens 304/384 e 0 to 1 dl 1389111101 ref 2 fl Rpc:N/0/0 rc 0/0&lt;br/&gt;
2014-01-07T17:11:41.567025+01:00 osiride-lp-041 kernel: Lustre: 23093:0:(client.c:1487:ptlrpc_expire_one_request()) Skipped 3 previous similar messages&lt;br/&gt;
2014-01-07T17:11:41.785397+01:00 osiride-lp-041 kernel: failure to allocate a tage (9)&lt;br/&gt;
2014-01-07T17:11:41.785412+01:00 osiride-lp-041 kernel: Lustre: home-OST0006-osc-ffff81063fc2f800: Connection to service home-OST0006 via nid 10.121.13.28@tcp was lost; in progress operations using this service will wait for recovery to complete.&lt;br/&gt;
2014-01-07T17:11:41.785416+01:00 osiride-lp-041 kernel: Lustre: Skipped 3 previous similar messages&lt;br/&gt;
2014-01-07T17:11:41.785421+01:00 osiride-lp-041 kernel: LustreError: 17973:0:(ldlm_request.c:1039:ldlm_cli_cancel_req()) Got rc -11 from cancel RPC: canceling anyway&lt;br/&gt;
2014-01-07T17:11:41.785426+01:00 osiride-lp-041 kernel: LustreError: 17973:0:(ldlm_request.c:1039:ldlm_cli_cancel_req()) Skipped 7 previous similar messages&lt;br/&gt;
2014-01-07T17:11:41.785430+01:00 osiride-lp-041 kernel: LustreError: 17973:0:(ldlm_request.c:1597:ldlm_cli_cancel_list()) ldlm_cli_cancel_list: -11&lt;br/&gt;
2014-01-07T17:11:41.785434+01:00 osiride-lp-041 kernel: LustreError: 17973:0:(ldlm_request.c:1597:ldlm_cli_cancel_list()) Skipped 7 previous similar messages&lt;br/&gt;
2014-01-07T17:11:41.814197+01:00 osiride-lp-041 kernel: failure to allocate a tage (18)&quot;&lt;/p&gt;</comment>
                            <comment id="74944" author="lustre.support" created="Tue, 14 Jan 2014 16:05:37 +0000"  >&lt;p&gt;Sorry for the misunderstanding. We need to know because the connection to home-OST0008, home-OST0008 and home-OST0006 was lost by client and the meaning of the &quot;failure to allocate a tage&quot; error.&lt;br/&gt;
Thanks&lt;/p&gt;</comment>
                            <comment id="74982" author="niu" created="Wed, 15 Jan 2014 03:27:24 +0000"  >&lt;p&gt;The &quot;failure to allocate a tage&quot; means Lustre logging system can&apos;t allocate buffer to store debug message, and the result is that some debug message will be lost. It won&apos;t break the connection between client and OSTs.&lt;/p&gt;

&lt;p&gt;So, client lost connection to OST0006, OST0007 and OST0008? and you want to know why the client lost connections?&lt;/p&gt;</comment>
                            <comment id="76703" author="lustre.support" created="Tue, 11 Feb 2014 08:16:09 +0000"  >&lt;p&gt;Hi, we want know because there has been the client lost of connection to OST0006, OST0007 and OST0008.&lt;/p&gt;

&lt;p&gt;Regards&lt;/p&gt;
</comment>
                            <comment id="77076" author="niu" created="Fri, 14 Feb 2014 12:49:16 +0000"  >&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;2014-01-07T17:11:57.274407+01:00 osiride-lp-041 kernel: Lustre: 7567:0:(&lt;span class=&quot;code-keyword&quot;&gt;import&lt;/span&gt;.c:517:import_select_connection()) home-OST000a-osc-ffff81063fc2f800: tried all connections, increasing latency to 3s
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I suspect it&apos;s a network problem, not related to the write failures (-122 EDUOT error).&lt;/p&gt;</comment>
                            <comment id="78030" author="gabriele.paciucci" created="Thu, 27 Feb 2014 17:27:17 +0000"  >&lt;p&gt;I have talked with the customer and we agreed that this is a network problem. We can close this issue. In case of other similar errors, we can activate the debug daemon in order to have more informations.&lt;/p&gt;</comment>
                            <comment id="78045" author="pjones" created="Thu, 27 Feb 2014 18:47:33 +0000"  >&lt;p&gt;ok - thanks Gabriele&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13978" name="messages" size="108962" author="lustre.support" created="Tue, 14 Jan 2014 14:35:09 +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|hzwcsn:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>12276</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>