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-7500 Lustre <p>This issue was created by maloo for Saurabh Tandan &lt;saurabh.tandan@intel.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.hpdd.intel.com/test_sets/a417b6d0-945f-11e5-a5ac-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/a417b6d0-945f-11e5-a5ac-5254006e85c2</a>.</p> <p>The sub-test lnet-selftest failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>test failed to respond and timed out </pre> </div></div> <p>lent-selftest got timed out and no other subtest ran. Could not find any useful information as log files were absent. </p> EL7.1 Server/SLES11 SP3 Client<br/> Master - Build# 3252 LU-7500

lnet-selftest: test failed to respond and timed out

Bug Minor Open Unresolved Amir Shehata Maloo Tue, 1 Dec 2015 01:18:21 +0000 Mon, 26 Jun 2017 18:36:11 +0000 Lustre 2.8.0 0 7 <p>master, build# 3264, 2.7.64 tag<br/> Regression:EL7.1 Server/SLES11 SP3 Client<br/> <a href="https://testing.hpdd.intel.com/test_sets/1d317972-9f2b-11e5-bf9b-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/1d317972-9f2b-11e5-bf9b-5254006e85c2</a></p> <p>Doug</p> <p>Could you please advise on this one?</p> <p>Thanks</p> <p>Peter</p> <p>The one suite_stdout log from <a href="https://testing.hpdd.intel.com/test_sets/6c6a9940-9f0a-11e5-ba94-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/6c6a9940-9f0a-11e5-ba94-5254006e85c2</a> shows this is a hang at unmount:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>16:37:57:CMD: shadow-9vm3 lsmod | grep lnet &gt; /dev/null &amp;&amp; lctl dl | grep ' ST ' 16:37:59:CMD: shadow-9vm3 grep -c /mnt/ost5' ' /proc/mounts 16:37:59:Stopping /mnt/ost5 (opts:-f) on shadow-9vm3 16:37:59:CMD: shadow-9vm3 umount -d -f /mnt/ost5 16:37:59:CMD: shadow-9vm3 lsmod | grep lnet &gt; /dev/null &amp;&amp; lctl dl | grep ' ST ' 16:37:59:CMD: shadow-9vm3 grep -c /mnt/ost6' ' /proc/mounts 16:37:59:Stopping /mnt/ost6 (opts:-f) on shadow-9vm3 16:37:59:CMD: shadow-9vm3 umount -d -f /mnt/ost6 16:38:00:CMD: shadow-9vm3 lsmod | grep lnet &gt; /dev/null &amp;&amp; lctl dl | grep ' ST ' 16:38:00:CMD: shadow-9vm3 grep -c /mnt/ost7' ' /proc/mounts 16:38:00:Stopping /mnt/ost7 (opts:-f) on shadow-9vm3 16:38:00:CMD: shadow-9vm3 umount -d -f /mnt/ost7 17:37:42:********** Timeout by autotest system ********** </pre> </div></div> <p>Unfortunately, there are no console logs from the OST that might indicate what the problem is.</p> <p>After speaking with Saurabh, the failure at <a href="https://testing.hpdd.intel.com/test_sets/6c6a9940-9f0a-11e5-ba94-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/6c6a9940-9f0a-11e5-ba94-5254006e85c2</a>, and that Andreas posted the portion of the suite_stdout, is probably <a href="https://jira.whamcloud.com/browse/LU-7326" title="ost-pools hangs on OST unmount" class="issue-link" data-issue-key="LU-7326"><del>LU-7326</del></a>/<a href="https://jira.whamcloud.com/browse/LU-7038" title="obdfilter-survey test_3a: (lu_object.c:1224:lu_device_fini()) ASSERTION( atomic_read(&amp;d-&gt;ld_ref) == 0 ) failed: Refcount is 3" class="issue-link" data-issue-key="LU-7038"><del>LU-7038</del></a> meaning it should not be considered as part of this ticket. </p> <p>The two remaining failures listed in this ticket so far are for tests between SLES clients and CentOS servers and the only information we have about the failures is from the suite_stdout log:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>19:44:42:-----============= acceptance-small: lnet-selftest ============----- Wed Dec 9 18:44:38 PST 2015 19:44:42:Running: bash /usr/lib64/lustre/tests/lnet-selftest.sh 19:44:42:CMD: shadow-14vm12,shadow-14vm7 /usr/sbin/lctl list_nids | grep tcp | cut -f 1 -d '@' 19:44:42:CMD: shadow-14vm5,shadow-14vm6 /usr/sbin/lctl list_nids | grep tcp | cut -f 1 -d '@' 19:44:42:Stopping clients: shadow-14vm5,shadow-14vm6 /mnt/lustre (opts:) 19:44:42:CMD: shadow-14vm5,shadow-14vm6 running=\$(grep -c /mnt/lustre' ' /proc/mounts); 19:44:42:if [ \$running -ne 0 ] ; then 19:44:42:echo Stopping client \$(hostname) /mnt/lustre opts:; 19:44:42:lsof /mnt/lustre || need_kill=no; 19:44:42:if [ x != x -a x\$need_kill != xno ]; then 19:44:42: pids=\$(lsof -t /mnt/lustre | sort -u); 19:44:42: if [ -n \"\$pids\" ]; then 19:44:42: kill -9 \$pids; 19:44:42: fi 19:44:42:fi; 19:44:42:while umount /mnt/lustre 2&gt;&amp;1 | grep -q busy; do 19:44:42: echo /mnt/lustre is still busy, wait one second &amp;&amp; sleep 1; 19:44:42:done; 19:44:42:fi 20:45:17:********** Timeout by autotest system ********** </pre> </div></div> <p>Another instance found for interop tag 2.7.66 - EL6.7 Server/2.7.1 Client, build# 3316<br/> <a href="https://testing.hpdd.intel.com/test_sets/70b97fbe-cc98-11e5-b80c-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/70b97fbe-cc98-11e5-b80c-5254006e85c2</a></p> <p>I hit similar trouble in conf-sanity<br/> <a href="https://testing.hpdd.intel.com/test_logs/64716322-2c90-11e6-bbf5-5254006e85c2/show_text" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_logs/64716322-2c90-11e6-bbf5-5254006e85c2/show_text</a></p> Development End date Wed, 23 Dec 2015 01:18:21 +0000 Rank 1|hzxujr: Rank (Obsolete) 9223372036854775807 Severity Start date Tue, 1 Dec 2015 01:18:21 +0000