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-11490 Lustre <p>Patch fixes rr_alloc() test to use FSNAME instead of lustre in the parameter path.</p> LU-11490

run_rr_alloc() defect: FSNAME should be used instead of lustre

Bug Minor Resolved Fixed WC Triage Elena Gryaznova esay Wed, 10 Oct 2018 13:50:38 +0000 Mon, 16 Dec 2019 12:58:03 +0000 Mon, 16 Dec 2019 12:58:03 +0000 Lustre 2.12.0 Lustre 2.14.0 0 5 <p>Elena Gryaznova (c17455@cray.com) uploaded a new patch: <a href="https://review.whamcloud.com/33333" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/33333</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-11490" title="run_rr_alloc() defect: FSNAME should be used instead of lustre" class="issue-link" data-issue-key="LU-11490"><del>LU-11490</del></a> tests: fix rr_alloc() test to use FSNAME<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 274f00cfe171a2215dd71a2dbab38fee8bd4fe4d</p> <p>Thanks for this patch. Are there other places in the test code that assume "lustre" is the fsname? </p> <p>I've been thinking that it would be useful to have a random FSNAME setting per test session so that we avoid tests being added that assume the wrong FSNAME, as well as avoid potential conflicts between running or stale filesystem components. In the past we've seen some issues during testing because of an old OSS or MDS VM with the same FSNAME is trying to join a newly-formatted filesystem, which breaks the currently-running testing in strange and hard-to-debug ways. </p> <p>I think there's a few more instances of assuming 'lustre' is the fs name in the Lustre test suites:</p> <p>sanity test 805</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> 19427 local old 19428 local quota 19429 local pref=<span class="code-quote">"osd-zfs.lustre-MDT0000."</span> 19430 19431 # limit available space on MDS dataset to meet nospace issue </pre> </div></div> <p>and sanityn test 93</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> 4237 local old_rr=$(do_facet $SINGLEMDS lctl get_param -n \ 4238 <span class="code-quote">'lod.lustre-MDT*/qos_threshold_rr'</span> | sed -e <span class="code-quote">'s/%<span class="code-comment">//'</span>) </span>4239 do_facet $SINGLEMDS lctl set_param -n \ 4240 <span class="code-quote">'lod.lustre-MDT*/qos_threshold_rr'</span> 100 4241 #define OBD_FAIL_MDS_LOV_CREATE_RACE 0x163 4242 do_facet $SINGLEMDS <span class="code-quote">"lctl set_param fail_loc=0x00000163"</span> 4243 4244 $SETSTRIPE -c -1 $DIR1/$tfile-1/file1 &amp; 4245 local PID1=$! 4246 sleep 1 4247 $SETSTRIPE -c -1 $DIR2/$tfile-2/file2 &amp; 4248 local PID2=$! 4249 wait $PID2 4250 wait $PID1 4251 do_facet $SINGLEMDS <span class="code-quote">"lctl set_param fail_loc=0x0"</span> 4252 do_facet $SINGLEMDS "lctl set_param -n \ 4253 <span class="code-quote">'lod.lustre-MDT*/qos_threshold_rr'</span> $old_rr" </pre> </div></div> <p>and sanity-flr test 33</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> 1040 # read file again with ost2 failed 1041 $LCTL set_param ldlm.namespaces.lustre-*-osc-ffff*.lru_size=clear </pre> </div></div> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/33333/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/33333/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-11490" title="run_rr_alloc() defect: FSNAME should be used instead of lustre" class="issue-link" data-issue-key="LU-11490"><del>LU-11490</del></a> tests: fix rr_alloc() test to use FSNAME<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: c0a1ef281a45fb0baf1f12a4282ea717efe9051d</p> <p>Elena's patch has landed for 2.12 but we should leave the ticket open until the other places have been fixed too</p> <p>James Nunez (jnunez@whamcloud.com) uploaded a new patch: <a href="https://review.whamcloud.com/36694" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/36694</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-11490" title="run_rr_alloc() defect: FSNAME should be used instead of lustre" class="issue-link" data-issue-key="LU-11490"><del>LU-11490</del></a> tests: use variable for file system name<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: ab64ee277197a093787b914421dbebaf70442c1a</p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/36694/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/36694/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-11490" title="run_rr_alloc() defect: FSNAME should be used instead of lustre" class="issue-link" data-issue-key="LU-11490"><del>LU-11490</del></a> tests: use variable for file system name<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 134f3eced1535bb6e867d552075d507eadb7cc48</p> <p>Landed for 2.14</p> Development Epic test Rank 1|i003xr: Rank (Obsolete) 9223372036854775807 Severity