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-11619 Lustre <p>While doing testing using ZFS I see sanity test 155 failing. The reason for this is that parametes like osd-<b>.</b>.writethrough_cache_enable don't exist for ZFS. Before it silently failed since it was accessing a broken symlink but now an error is reported back to user land if you attempt to set these parameters on ZFS.</p> lustre 2.12 on clients and servers with ZFS backend. LU-11619

sanity test 155 fail for ZFS

Bug Major Open Unresolved Sarah Liu James A Simmons Mon, 5 Nov 2018 20:11:46 +0000 Tue, 19 Apr 2022 18:46:39 +0000 Lustre 2.12.0 0 5 <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=jamesanunez" class="user-hover" rel="jamesanunez">jamesanunez</a></p> <p>Are we seeing this in our testing?</p> <p>Peter</p> <p>Yes, we do see this error, but the test does not fail because of it since we are not checking that the call to 'lctl get/set_param' succeeds. Looking at a recent full test session for b2_10 at <a href="https://testing.whamcloud.com/test_sets/16603dd4-df08-11e8-a871-52540065bddc" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/16603dd4-df08-11e8-a871-52540065bddc</a>, we see</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>== sanity test 155a: Verify small file correctness: read cache:on write_cache:on ===================== 17:10:46 (1541092246) CMD: trevis-11vm8 params=\$(/usr/sbin/lctl get_param obdfilter.*.writethrough_cache_enable); [[ -z \"lustre-OST0000\" ]] &amp;&amp; param= || param=\$(grep lustre-OST0000 &lt;&lt;&lt; \"\$params\"); [[ -z \$param ]] &amp;&amp; param=\"\$params\"; while read s; do echo ost1 \$s; done &lt;&lt;&lt; \"\$param\" trevis-11vm8: error: get_param: param_path 'obdfilter/*/writethrough_cache_enable': No such file or directory </pre> </div></div> <p>From sanity.sh</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> 11874 save_writethrough() { 11875 local facets=$(get_facets OST) 11876 11877 save_lustre_params $facets <span class="code-quote">"osd-*.*.writethrough_cache_enable"</span> &gt; $1 11878 } 11879 11880 test_155a() { 11881 [ $PARALLEL == <span class="code-quote">"yes"</span> ] &amp;&amp; skip <span class="code-quote">"skip parallel run"</span> 11882 11883 local p=<span class="code-quote">"$TMP/$TESTSUITE-$TESTNAME.parameters"</span> 11884 11885 save_writethrough $p 11886 11887 set_cache read on 11888 set_cache writethrough on 11889 test_155_small_load 11890 restore_lustre_params &lt; $p 11891 rm -f $p 11892 } 11893 run_test 155a <span class="code-quote">"Verify small file correctness: read cache:on write_cache:on"</span> </pre> </div></div> <p>Alex, is there any reason we would want the ability to turn writethrough cache OFF for ZFS? AFAIK, this would completely kill ZFS performance and is undesirable. In that case, we should just skip tests that turn writethrough cache off for ZFS. </p> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=adilger" class="user-hover" rel="adilger">adilger</a>well, I guess it's impossible technically. even with ZIL it's still going though ARC, AFAIK.</p> <p>As Andreas stated above, we should skip all tests that turn writethrough cache off for ZFS. </p> <p>Since the writethrough_cache_enable parameter doesn't exist for OSSs with ZFS file systems, should we skip all tests that try to turn on, off or query writethrough_cache_enable?</p> Development Rank 1|i005qf: Rank (Obsolete) 9223372036854775807 Severity