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-1912 Lustre <p>This issue was created by maloo for Minh Diep &lt;mdiep@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/0e62c5d6-fa97-11e1-887d-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/0e62c5d6-fa97-11e1-887d-52540035b04c</a>.</p> <p>survey:/usr/lib64/lustre/tests:/usr/lib64/lustre/utils/gss:/usr/lib64/lustre/utils:/usr/lib64/openmpi/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin: NAME=autotest_config sh rpc.sh check_logdir /home/autotest/.autotest/shared_dir/2012-09-08/054638-7fbcd5d87e28 <br/> lfsck : @@@@@@ FAIL: /home/autotest/.autotest/shared_dir/2012-09-08/054638-7fbcd5d87e28 isn't a shared directory <br/> Trace dump:<br/> = /usr/lib64/lustre/tests/test-framework.sh:3642:error_noexit()<br/> = /usr/lib64/lustre/tests/test-framework.sh:3664:error()<br/> = /usr/lib64/lustre/tests/test-framework.sh:3219:generate_db()<br/> = /usr/lib64/lustre/tests/lfsck.sh:260:main()</p> <p>It's strange to me the different lustre version (b2_2 and b2_3) between server and client would cause above issue. I tried on a cluster with all b2_3 and it worked for the exact some dir (ie /scratch/mdiep/tmp)</p> LU-1912

Test failure on test suite lfsck

Bug Blocker Resolved Fixed Jian Yu Maloo Wed, 12 Sep 2012 13:41:16 +0000 Thu, 20 Sep 2012 00:45:44 +0000 Thu, 20 Sep 2012 00:45:44 +0000 Lustre 2.2.0 Lustre 2.3.0 Lustre 2.4.0 Lustre 2.3.0 Lustre 2.4.0 0 3 <p>on b2_3</p> <p>check_write_access() {<br/> local dir=$1<br/> local node<br/> local file</p> <p> for node in $(nodes_list); do<br/> file=$dir/check_file.$(short_hostname $node)<br/> if [[ ! -f "$file" ]]; then</p> <ol> <li>Logdir not accessible/writable from this node.<br/> return 1<br/> fi<br/> rm -f $file || return 1<br/> done<br/> return 0<br/> }</li> </ol> <p>on b2_2</p> <p>check_write_access() {<br/> local dir=$1<br/> for node in $(nodes_list); do<br/> if [ ! -f "$dir/node.$(short_hostname ${node}).yml" ]; then</p> <ol> <li>Logdir not accessible/writable from this node.<br/> return 1<br/> fi<br/> done<br/> rm -f $dir/node.*.yml<br/> return 0<br/> }</li> </ol> <p>This means running b2_3 &lt;-&gt; b2_2 will cause this issue because the file created and expected to exist will be different. I don't have a good solution for this. Let's check with Yujian</p> <p>Yujian</p> <p>Could you please look into this one?</p> <p>Thanks</p> <p>Peter</p> <p>The patch for <a href="https://jira.whamcloud.com/browse/LU-1255" title="recovery-mds-scale FAIL: rundbench: no client file found for dbench DBENCH_LIB= SRC=" class="issue-link" data-issue-key="LU-1255"><del>LU-1255</del></a> in <a href="http://review.whamcloud.com/#change,2376" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,2376</a> needs to be landed on Lustre b2_2 branch.</p> <p>Yujian</p> <p>We don't have any plans to land anything to b2_2 at this time. Is there a way to just skip this test when interoperating with 2.2? If not then this test failure will disappear when we switching to the 2.4 interop matrix.</p> <p>Peter</p> <p>If approve, I think we can check and skip server or client run b2_2 or b2_3</p> <p>Hi Peter,<br/> For 2.3 client and 2.2 server, we can add Lustre version check code in 2.3 test suite to skip the test.<br/> For 2.2 client and 2.3 server, I think there is no proper way.</p> <p>Lustre client build: <a href="http://build.whamcloud.com/job/lustre-b2_2/17" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_2/17</a><br/> Lustre server build: <a href="http://build.whamcloud.com/job/lustre-b2_3/19" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_3/19</a><br/> Distro/Arch: RHEL6.3/x86_64<br/> The same issue occurred: <a href="https://maloo.whamcloud.com/test_sets/d84f0c0e-ff5d-11e1-bce0-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/d84f0c0e-ff5d-11e1-bce0-52540035b04c</a></p> <p>Patch for master branch: <a href="http://review.whamcloud.com/4021" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4021</a><br/> It also needs to be cherry-picked to b2_3 branch.</p> <p>Landed for 2.3 and 2.4</p> Development Rank 1|hzv5jb: Rank (Obsolete) 4431 Severity