<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:34:18 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-17301] Client mount hangs for several minutes</title>
                <link>https://jira.whamcloud.com/browse/LU-17301</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;After patch &lt;a href=&quot;https://review.whamcloud.com/c/fs/lustre-release/+/51329,&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/c/fs/lustre-release/+/51329,&lt;/a&gt; client mount hangs for several minutes when using `llmount.sh`. When this patch is reverted, the mount completes in a normal amount of time.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Setup:&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;
Kernel - 5.15.94
openZFS - 2.1.99-1735_gdc72c60ec
Distro - CentOS Linux release 8.5.2111
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Kernel messages:&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;
[ &#160;480.629670] Lustre: mdt_rdpg01_001: service thread pid 52665 was inactive &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; 40.946 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; debugging purposes:
[ &#160;480.632948] Pid: 52665, comm: mdt_rdpg01_001 5.15.94 #1 SMP Fri Feb 17 01:05:48 UTC 2023
[ &#160;480.634352] Call Trace TBD:
[ &#160;500.084741] LustreError: 52665:0:(upcall_cache.c:251:upcall_cache_get_entry()) acquire &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; key 0: error -110
[ &#160;500.086740] Lustre: Mounted lustre-client&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;The mount hangs for several minutes even after the &apos;Mounted&apos; message gets printed.&lt;/p&gt;</description>
                <environment></environment>
        <key id="79088">LU-17301</key>
            <summary>Client mount hangs for several minutes</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="stancheff">Shaun Tancheff</assignee>
                                    <reporter username="timday">Tim Day</reporter>
                        <labels>
                    </labels>
                <created>Mon, 20 Nov 2023 16:49:56 +0000</created>
                <updated>Wed, 13 Dec 2023 15:22:26 +0000</updated>
                            <resolved>Wed, 13 Dec 2023 15:22:26 +0000</resolved>
                                                    <fixVersion>Lustre 2.16.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                            <comments>
                            <comment id="393642" author="pjones" created="Mon, 20 Nov 2023 16:55:01 +0000"  >&lt;p&gt;Probably the immediate step should be to revert this patch from master until a fix can be worked out...&lt;/p&gt;</comment>
                            <comment id="393687" author="arshad512" created="Tue, 21 Nov 2023 04:38:56 +0000"  >&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;$ uname -r
3.10.0-1160.15.2.el7.x86_64
$ cat /etc/redhat-release&#160;
CentOS Linux release 7.9.2009 (Core)&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Also seen on 4.X series kernel. (el8). &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;Nov 20 23:25:51 centos79 kernel: Lustre: mdt_rdpg00_001: service thread pid 8735 was inactive for 40.059 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
Nov 20 23:25:51 centos79 kernel: Pid: 8735, comm: mdt_rdpg00_001 3.10.0-1160.15.2.el7.x86_64 #1 SMP Wed Feb 3 15:06:38 UTC 2021
Nov 20 23:25:51 centos79 kernel: Call Trace:
Nov 20 23:25:51 centos79 kernel: [&amp;lt;0&amp;gt;] upcall_cache_get_entry+0x201/0x9d0 [obdclass]
Nov 20 23:25:51 centos79 kernel: [&amp;lt;0&amp;gt;] mdt_identity_get+0x17/0x50 [mdt]
Nov 20 23:25:51 centos79 kernel: [&amp;lt;0&amp;gt;] old_init_ucred_common+0xed/0x2c0 [mdt]
Nov 20 23:25:51 centos79 kernel: [&amp;lt;0&amp;gt;] mdt_init_ucred+0x19c/0x320 [mdt]
Nov 20 23:25:51 centos79 kernel: [&amp;lt;0&amp;gt;] mdt_getattr+0x156/0x640 [mdt]
Nov 20 23:25:51 centos79 kernel: [&amp;lt;0&amp;gt;] tgt_request_handle+0x743/0x19a0 [ptlrpc]
Nov 20 23:25:51 centos79 kernel: [&amp;lt;0&amp;gt;] ptlrpc_server_handle_request+0x261/0xcd0 [ptlrpc]
Nov 20 23:25:51 centos79 kernel: [&amp;lt;0&amp;gt;] ptlrpc_main+0xc5c/0x16c0 [ptlrpc]
Nov 20 23:25:51 centos79 kernel: [&amp;lt;0&amp;gt;] kthread+0xd1/0xe0
Nov 20 23:25:51 centos79 kernel: [&amp;lt;0&amp;gt;] ret_from_fork_nospec_begin+0xe/0x21
Nov 20 23:25:51 centos79 kernel: [&amp;lt;0&amp;gt;] 0xfffffffffffffffe
Nov 20 23:26:11 centos79 kernel: LustreError: 8735:0:(upcall_cache.c:244:upcall_cache_get_entry()) acquire for key 0: error -110
Nov 20 23:26:11 centos79 kernel: Lustre: Mounted lustre-client
Nov 20 23:26:52 centos79 kernel: Lustre: mdt00_002: service thread pid 8733 was inactive for 40.169 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
Nov 20 23:26:52 centos79 kernel: Pid: 8733, comm: mdt00_002 3.10.0-1160.15.2.el7.x86_64 #1 SMP Wed Feb 3 15:06:38 UTC 2021
Nov 20 23:26:52 centos79 kernel: Call Trace:
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] upcall_cache_get_entry+0x201/0x9d0 [obdclass]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] mdt_identity_get+0x17/0x50 [mdt]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] old_init_ucred_common+0xed/0x2c0 [mdt]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] mdt_init_ucred+0x19c/0x320 [mdt]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] mdt_intent_getattr+0xc3/0x4b0 [mdt]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] mdt_intent_opc+0x1c5/0xc40 [mdt]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] mdt_intent_policy+0xfa/0x460 [mdt]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] ldlm_lock_enqueue+0x3a4/0xb80 [ptlrpc]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] ldlm_handle_enqueue+0x34d/0x17a0 [ptlrpc]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] tgt_enqueue+0x68/0x240 [ptlrpc]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] tgt_request_handle+0x743/0x19a0 [ptlrpc]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] ptlrpc_server_handle_request+0x261/0xcd0 [ptlrpc]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] ptlrpc_main+0xc5c/0x16c0 [ptlrpc]
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] kthread+0xd1/0xe0
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] ret_from_fork_nospec_begin+0xe/0x21
Nov 20 23:26:52 centos79 kernel: [&amp;lt;0&amp;gt;] 0xfffffffffffffffe
Nov 20 23:27:12 centos79 kernel: LustreError: 8733:0:(upcall_cache.c:244:upcall_cache_get_entry()) acquire for key 0: error -110&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="393719" author="zam" created="Tue, 21 Nov 2023 11:51:34 +0000"  >&lt;p&gt;Hello Arshad,&lt;/p&gt;

&lt;p&gt;can you please test the following patch:&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;
diff --git a/lustre/utils/l_getidentity.c b/lustre/utils/l_getidentity.c
index 34c70d8d71..f99bdafc23 100644
--- a/lustre/utils/l_getidentity.c
+++ b/lustre/utils/l_getidentity.c
@@ -67,7 +67,7 @@ &lt;span class=&quot;code-keyword&quot;&gt;static&lt;/span&gt; &lt;span class=&quot;code-object&quot;&gt;int&lt;/span&gt; nss_pw_buf_len;
 &lt;span class=&quot;code-keyword&quot;&gt;static&lt;/span&gt; void *nss_pw_buf;
 &lt;span class=&quot;code-keyword&quot;&gt;static&lt;/span&gt; &lt;span class=&quot;code-object&quot;&gt;int&lt;/span&gt; nss_grent_buf_len;
 &lt;span class=&quot;code-keyword&quot;&gt;static&lt;/span&gt; void *nss_grent_buf;
-&lt;span class=&quot;code-keyword&quot;&gt;static&lt;/span&gt; &lt;span class=&quot;code-object&quot;&gt;int&lt;/span&gt; g_n_nss_modules;
+&lt;span class=&quot;code-keyword&quot;&gt;static&lt;/span&gt; &lt;span class=&quot;code-object&quot;&gt;int&lt;/span&gt; g_n_nss_modules = 0;
 &lt;span class=&quot;code-keyword&quot;&gt;static&lt;/span&gt; &lt;span class=&quot;code-object&quot;&gt;int&lt;/span&gt; grent_mod_no = -1;
 
 struct nss_module {

&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;unfortunately I cannot reproduce the problem quickly.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Zam.&lt;/p&gt;</comment>
                            <comment id="393721" author="gerrit" created="Tue, 21 Nov 2023 11:55:38 +0000"  >&lt;p&gt;&quot;Alexander Zarochentsev &amp;lt;alexander.zarochentsev@hpe.com&amp;gt;&quot; uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/c/fs/lustre-release/+/53191&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/c/fs/lustre-release/+/53191&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-17301&quot; title=&quot;Client mount hangs for several minutes&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-17301&quot;&gt;&lt;del&gt;LU-17301&lt;/del&gt;&lt;/a&gt; utils: l_getidentity nss init fix&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 1794102c4b4b17f364715e3a9611191945bd5d77&lt;/p&gt;</comment>
                            <comment id="393724" author="arshad512" created="Tue, 21 Nov 2023 12:19:07 +0000"  >&lt;p&gt;Hi Zam,&lt;/p&gt;

&lt;p&gt;Sorry, it did not work.&#160; I am getting this by just doing llmount.sh&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;Nov 21 07:15:56 centos79 kernel: Lustre: mdt_rdpg00_001: service thread pid 10702 was inactive for 40.000 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
Nov 21 07:15:56 centos79 kernel: Pid: 10702, comm: mdt_rdpg00_001 3.10.0-1160.15.2.el7.x86_64 #1 SMP Wed Feb 3 15:06:38 UTC 2021
Nov 21 07:15:56 centos79 kernel: Call Trace:
Nov 21 07:15:56 centos79 kernel: [&amp;lt;0&amp;gt;] upcall_cache_get_entry+0x201/0xa00 [obdclass]
Nov 21 07:15:56 centos79 kernel: [&amp;lt;0&amp;gt;] mdt_identity_get+0x17/0x50 [mdt]
Nov 21 07:15:56 centos79 kernel: [&amp;lt;0&amp;gt;] old_init_ucred_common+0xed/0x2c0 [mdt]
Nov 21 07:15:56 centos79 kernel: [&amp;lt;0&amp;gt;] mdt_init_ucred+0x19c/0x320 [mdt]
Nov 21 07:15:56 centos79 kernel: [&amp;lt;0&amp;gt;] mdt_getattr+0x156/0x640 [mdt]
Nov 21 07:15:56 centos79 kernel: [&amp;lt;0&amp;gt;] tgt_request_handle+0x743/0x19a0 [ptlrpc]
Nov 21 07:15:56 centos79 kernel: [&amp;lt;0&amp;gt;] ptlrpc_server_handle_request+0x261/0xcd0 [ptlrpc]
Nov 21 07:15:56 centos79 kernel: [&amp;lt;0&amp;gt;] ptlrpc_main+0xc5c/0x16c0 [ptlrpc]
Nov 21 07:15:56 centos79 kernel: [&amp;lt;0&amp;gt;] kthread+0xd1/0xe0
Nov 21 07:15:56 centos79 kernel: [&amp;lt;0&amp;gt;] ret_from_fork_nospec_begin+0xe/0x21
Nov 21 07:15:56 centos79 kernel: [&amp;lt;0&amp;gt;] 0xfffffffffffffffe
Nov 21 07:16:16 centos79 kernel: LustreError: 10702:0:(upcall_cache.c:251:upcall_cache_get_entry()) acquire for key 0: error -110&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="393801" author="zam" created="Tue, 21 Nov 2023 23:37:35 +0000"  >&lt;p&gt;Looks like the following hunk (except -ldl) in the original patch is not needed:&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;
diff --git a/lustre/utils/Makefile.am b/lustre/utils/Makefile.am
index 56f67afd1d..bee65a1178 100644
--- a/lustre/utils/Makefile.am
+++ b/lustre/utils/Makefile.am
@@ -245,8 +245,9 @@ l_foreign_symlink_LDADD := $(top_builddir)/libcfs/libcfs/libcfs.la
 l_foreign_symlink_DEPENDENCIES := $(top_builddir)/libcfs/libcfs/libcfs.la
 
 l_getidentity_SOURCES = l_getidentity.c
-l_getidentity_LDADD := $(top_builddir)/libcfs/libcfs/libcfs.la
-l_getidentity_DEPENDENCIES := $(top_builddir)/libcfs/libcfs/libcfs.la
+l_getidentity_LDADD := $(top_builddir)/libcfs/libcfs/libcfs.la liblustreapi.la $(LIBPTLCTL)
+l_getidentity_LDFLAGS = -ldl
+l_getidentity_DEPENDENCIES := $(top_builddir)/libcfs/libcfs/libcfs.la liblustreapi.la $(LIBPTLCTL)
 
 lhsmtool_posix_SOURCES = lhsmtool_posix.c pid_file.c pid_file.h
 lhsmtool_posix_LDADD := liblustreapi.la $(PTHREAD_LIBS) \
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Moreover, it causes the shell wrapper lustre/utils/l_getidentity to fail silently when started by a kernel thread. The  tool is not a binary file but a shell wrapper when I start Lustre from the source dir by llmount.sh:&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;root@rocky lustre-release]# file lustre/utils/l_getidentity
lustre/utils/l_getidentity: POSIX shell script, ASCII text executable, with very long lines
[root@rocky lustre-release]# 
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The failures cause lustre client mount delays.&lt;/p&gt;</comment>
                            <comment id="393808" author="simmonsja" created="Wed, 22 Nov 2023 00:14:58 +0000"  >&lt;p&gt;The reason for the shell wrapper is that allows running in the sandbox that people love to do. This way l_getindentity can find the proper libraries independent if its in source tree or installed into an image. If this application is important enough maybe we strip its need of any external libraries. If I remember correctly it only needs liblustreapi.so for mdt/%s/identity_info. Perhaps we can migrate to a udev rule that spins up l_getidentity instead. Another option is we use globs directly instead of cfs_get_param_paths(). BY the way why -ldl directly. Seems to want to work around the whole libtool handlng.&lt;/p&gt;</comment>
                            <comment id="393817" author="arshad512" created="Wed, 22 Nov 2023 02:13:58 +0000"  >&lt;p&gt;Zam, your latest patch does work. Both on 7.9 and 8.4.&lt;/p&gt;

&lt;p&gt;&amp;gt;The tool is not a binary file but a shell wrapper when I start Lustre from the source dir by llmount.sh:...&lt;/p&gt;

&lt;p&gt;The binaries are normally kept under lustre/utils/.libs/.&lt;/p&gt;

&lt;p&gt;&#160;&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;# file lustre/utils/.libs/l_getidentity&#160;
lustre/utils/.libs/l_getidentity: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=b3cb5b448ee43365845f5d1fcb0a349bf91877c6, with debug_info, not stripped&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;The targets are normally names lustre/utils/.libs/lt-* (example lfs and lctl) along with with real name&lt;/p&gt;

&lt;p&gt;&#160;&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;# ls lustre/utils/.libs/lt-*
lustre/utils/.libs/lt-lctl &#160;lustre/utils/.libs/lt-lfs
&#160;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;l_getidentity does not have lt-&amp;lt;target&amp;gt;. I am not sure if this is causing the issue.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="393830" author="zam" created="Wed, 22 Nov 2023 08:14:11 +0000"  >&lt;p&gt;I intercepted the error stream output of l_getidentity being called by a Lustre server, and got something like:&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;[root@rocky ~]# cat /tmp/identity.log 
PATH=/sbin:/usr/sbin
0
upcall start lustre-MDT0000 0
/mnt/nfs/git/lustre-release/lustre/utils/l_getidentity: line 150: ls: command not found
/mnt/nfs/git/lustre-release/lustre/utils/l_getidentity: line 197: rm: command not found
/mnt/nfs/git/lustre-release/lustre/utils/l_getidentity: line 211: rm: command not found
/mnt/nfs/git/lustre-release/lustre/utils/l_getidentity: line 212: mv: command not found
/mnt/nfs/git/lustre-release/lustre/utils/l_getidentity: line 213: rm: command not found
upcall end lustre-MDT0000 0
0
[root@rocky ~]# 

&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I.e. the shell wrapper uses core linux utilities from /bin but PATH contains only &quot;/sbin&quot; and &quot;/usr/sbin&quot; , it is the reason for the libtool shell wrapper to function incorrectly.  If I add &quot;/bin:/usr/bin&quot; to the PATH variable, the upcall (in its shell variant) starts to work.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Zam.&lt;/p&gt;</comment>
                            <comment id="393837" author="arshad512" created="Wed, 22 Nov 2023 09:25:10 +0000"  >&lt;p&gt;I looked into an old vm and looks like lustre/utils/l_getidentity was always a binary and not a shell wrapper or launcher script.&lt;/p&gt;</comment>
                            <comment id="393888" author="zam" created="Wed, 22 Nov 2023 14:34:02 +0000"  >&lt;p&gt;&amp;gt;I looked into an old vm and looks like lustre/utils/l_getidentity was always a binary and not a shell wrapper or launcher script.&lt;/p&gt;

&lt;p&gt;yes, the patch converts it to a binary again.&lt;/p&gt;</comment>
                            <comment id="396596" author="gerrit" created="Wed, 13 Dec 2023 12:22:59 +0000"  >&lt;p&gt;&quot;Oleg Drokin &amp;lt;green@whamcloud.com&amp;gt;&quot; merged in patch &lt;a href=&quot;https://review.whamcloud.com/c/fs/lustre-release/+/53191/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/c/fs/lustre-release/+/53191/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-17301&quot; title=&quot;Client mount hangs for several minutes&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-17301&quot;&gt;&lt;del&gt;LU-17301&lt;/del&gt;&lt;/a&gt; utils: l_getidentity build fix&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 8fce6b40f245c438691800f6e239539a66e2395c&lt;/p&gt;</comment>
                            <comment id="396637" author="pjones" created="Wed, 13 Dec 2023 15:22:26 +0000"  >&lt;p&gt;Landed for 2.16&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="76577">LU-16901</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <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|i0428n:</customfieldvalue>

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