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-2023 Lustre <p>This issue was created by maloo for sarah &lt;sarah@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/b2d86c02-0658-11e2-9b17-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/b2d86c02-0658-11e2-9b17-52540035b04c</a>.</p> <p>From the test report, all sub tests passed while at the end of suite log shows:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>client-26vm6: mount.lustre: mount client-26vm3@tcp:/lustre at /mnt/lustre failed: File exists parallel-scale-nfsv3 : @@@@@@ FAIL: failed to mount lustre after nfs test Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:3645:error_noexit() = /usr/lib64/lustre/tests/parallel-scale-nfs.sh:106:main() == parallel-scale-nfsv3 parallel-scale-nfs.sh test complete, duration 4952 sec == 00:49:32 (1348472972) /usr/lib64/lustre/tests/parallel-scale-nfs.sh: FAIL: failed to mount lustre after nfs test NFSCLIENT mode: setup, cleanup, check config skipped CMD: client-26vm5,client-26vm6.lab.whamcloud.com echo \$(hostname); grep ' '/mnt/lustre' ' /proc/mounts client-26vm5.lab.whamcloud.com 10.10.4.150@tcp:/lustre /mnt/lustre lustre rw,flock,user_xattr 0 0 client-26vm6.lab.whamcloud.com parallel-scale-nfsv3 : @@@@@@ FAIL: NFSCLIENT=true mode, but no NFS export found! Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:3645:error_noexit() </pre> </div></div> Server/Client lustre-b2_3-RC1 RHEL6 LU-2023

Test failure on test suite parallel-scale-nfsv3

Bug Minor Resolved Cannot Reproduce Minh Diep Maloo Mon, 24 Sep 2012 17:20:26 +0000 Fri, 2 Dec 2016 17:02:38 +0000 Fri, 2 Dec 2016 17:02:38 +0000 Lustre 2.3.0 0 5 <p>Minh</p> <p>Could you please advise on this one?</p> <p>thanks</p> <p>Peter</p> <p>found this on the mds/nfs server (client-26vm3) console.</p> <p>00:39:05:Lustre: DEBUG MARKER: == parallel-scale-nfsv3 test iorfpp: iorfpp == 00:38:56 (1348472336)<br/> 00:39:05:Lustre: DEBUG MARKER: lfs setstripe /mnt/lustre/d0.ior.fpp -c -1<br/> 00:42:57:rpc-srv/tcp: nfsd: got error -32 when sending 140 bytes - shutting down socket &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;<br/> 00:49:29:Lustre: DEBUG MARKER: lctl set_param -n fail_loc=0 2&gt;/dev/null || true<br/> 00:49:29:Lustre: DEBUG MARKER: rc=$([ -f /proc/sys/lnet/catastrophe ] &amp;&amp; echo $(&lt; /proc/sys/lnet/catastrophe) || echo 0);<br/> 00:49:29:if [ $rc -ne 0 ]; then echo $(hostname): $rc; fi<br/> 00:49:29:exit $rc;<br/> 00:49:30:Lustre: DEBUG MARKER: service nfs stop</p> <p>I think this is nfs issue under stress test. This results in nfs shutdown was not completed, hence when lustre mount would fail to do (-17) file exist.</p> <p>I would like to get a second opinion on this.</p> <p>FanYong,</p> <p>could you comment?</p> <p>I do not think so. I found some logs on the Lustre client (client2, client-26vm6):</p> <p>=====================================<br/> 00:49:41:LustreError: 11188:0:(genops.c:309:class_newdev()) Device lustre-MDT0000-mdc-ffff88005073c800 already exists at 13, won't add<br/> 00:49:41:LustreError: 11188:0:(obd_config.c:365:class_attach()) Cannot create device lustre-MDT0000-mdc-ffff88005073c800 of type mdc : -17<br/> 00:49:41:LustreError: 11188:0:(obd_config.c:1499:class_config_llog_handler()) Err -17 on cfg command:<br/> 00:49:41:Lustre: cmd=cf001 0:lustre-MDT0000-mdc 1:mdc 2:lustre-clilmv_UUID <br/> 00:49:41:LustreError: 15c-8: MGC10.10.4.150@tcp: The configuration from log 'lustre-client' failed (-17). This may be the result of communication errors between this node and the MGS, a bad configuration, or other errors. See the syslog for more information.<br/> 00:49:41:LustreError: 11185:0:(llite_lib.c:998:ll_fill_super()) Unable to process log: -17<br/> 00:49:41:Lustre: Unmounted lustre-client<br/> 00:49:41:LustreError: 11185:0:(ldlm_request.c:1166:ldlm_cli_cancel_req()) Got rc -108 from cancel RPC: canceling anyway<br/> 00:49:41:LustreError: 11185:0:(ldlm_request.c:1166:ldlm_cli_cancel_req()) Skipped 1 previous similar message<br/> 00:49:41:LustreError: 11185:0:(ldlm_request.c:1792:ldlm_cli_cancel_list()) ldlm_cli_cancel_list: -108<br/> 00:49:41:LustreError: 11185:0:(ldlm_request.c:1792:ldlm_cli_cancel_list()) Skipped 1 previous similar message<br/> 00:49:41:LustreError: 11185:0:(obd_mount.c:2569:lustre_fill_super()) Unable to mount (-17)<br/> 00:49:41:Lustre: DEBUG MARKER: /usr/sbin/lctl mark parallel-scale-nfsv3 : @@@@@@ FAIL: failed to mount lustre after nfs test<br/> =====================================</p> <p>I do not know the system configuration exactly. But I guess the client2 is NFS server, right? If yes, then just because the Lustre client fail to mount client-26vm3 (MDS&amp;MGS), then cause NFS server re-export failure. As for why client2 failed to mount, it seems related with former uncleaned environment:</p> <p>===================================<br/> struct obd_device *class_newdev(const char *type_name, const char *name)<br/> {<br/> ...</p> <p> if (obd &amp;&amp; obd-&gt;obd_name &amp;&amp;<br/> (strcmp(name, obd-&gt;obd_name) == 0)) {<br/> CERROR("Device %s already exists at %d, won't add\n",<br/> name, i);<br/> if (result) </p> { LASSERTF(result-&gt;obd_magic == OBD_DEVICE_MAGIC, "%p obd_magic %08x != %08x\n", result, result-&gt;obd_magic, OBD_DEVICE_MAGIC); LASSERTF(result-&gt;obd_minor == new_obd_minor, "%p obd_minor %d != %d\n", result, result-&gt;obd_minor, new_obd_minor); obd_devs[result-&gt;obd_minor] = NULL; result-&gt;obd_name[0]='\0'; } <p> result = ERR_PTR(-EEXIST);<br/> break;<br/> }<br/> ...<br/> }<br/> ===================================</p> <p>We need the lustre kernel log to find why the environment is not cleaned. Without such log, we cannot know much.</p> <p>Fanyoung, you can find lustre debug log here on brent<br/> /home/autotest/logdir/test_logs/2012-09-22/lustre-b2_3-el6-x86_64_<em>24</em>_-7f2b7f4b9360/parallel-scale-nfsv3..debug_log*</p> Development Rank 1|hzv3sn: Rank (Obsolete) 4142 Severity