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-8738 Lustre <p>sanity test 255b failed as follows:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>== sanity test 255b: check 'lfs ladvise -a dontneed' ================================================= 17:21:04 (1476811264) 100+0 records in 100+0 records out 104857600 bytes (105 MB) copied, 0.778124 s, 135 MB/s CMD: trevis-41vm4 cat /proc/meminfo | grep ^MemTotal: Total memory: 1923480 KiB CMD: trevis-41vm4 sync &amp;&amp; echo 3 &gt; /proc/sys/vm/drop_caches CMD: trevis-41vm4 cat /proc/meminfo | grep ^Cached: Cache used before read: 72592 KiB CMD: trevis-41vm4 cat /proc/meminfo | grep ^Cached: Cache used after read: 120972 KiB CMD: trevis-41vm4 cat /proc/meminfo | grep ^Cached: Cache used after dontneed ladvise: 18572 KiB sanity test_255b: @@@@@@ FAIL: Ladvise willread should use more memory than 76800 KiB </pre> </div></div> <p>Maloo reports:<br/> <a href="https://testing.hpdd.intel.com/test_sets/c98e8654-9d15-11e6-9f24-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/c98e8654-9d15-11e6-9f24-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/f1a59ea0-9605-11e6-a96f-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/f1a59ea0-9605-11e6-a96f-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/ba662914-9588-11e6-9722-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/ba662914-9588-11e6-9722-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/793fd440-95af-11e6-a96f-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/793fd440-95af-11e6-a96f-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/14b006f8-956e-11e6-9fed-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/14b006f8-956e-11e6-9fed-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/7d75d880-8b9a-11e6-a8b7-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/7d75d880-8b9a-11e6-a8b7-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/abe41d90-895f-11e6-a8b7-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/abe41d90-895f-11e6-a8b7-5254006e85c2</a></p> LU-8738

sanity test_255b: FAIL: Ladvise willread should use more memory than 76800 KiB

Bug Critical Resolved Fixed James Nunez Jian Yu Thu, 20 Oct 2016 07:12:24 +0000 Mon, 21 Nov 2016 20:39:29 +0000 Mon, 21 Nov 2016 20:39:28 +0000 Lustre 2.9.0 Lustre 2.9.0 0 13 <p>+1 on master:<br/> <a href="https://testing.hpdd.intel.com/test_sets/27db5292-a468-11e6-8a63-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/27db5292-a468-11e6-8a63-5254006e85c2</a></p> <p>another on master:<br/> <a href="https://testing.hpdd.intel.com/test_sets/e7949930-a88d-11e6-882e-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/e7949930-a88d-11e6-882e-5254006e85c2</a></p> <p>On master:</p> <p><a href="https://testing.hpdd.intel.com/test_sets/37218620-ab04-11e6-a726-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/37218620-ab04-11e6-a726-5254006e85c2</a></p> <p>Note that ladvise willread used almost 76800 KiB.</p> <p>Again on master:</p> <p><a href="https://testing.hpdd.intel.com/test_sets/a6324fec-ab84-11e6-a76e-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/a6324fec-ab84-11e6-a76e-5254006e85c2</a></p> <p>One more failure instance on master branch:<br/> <a href="https://testing.hpdd.intel.com/test_sets/7e484224-aa8b-11e6-a095-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/7e484224-aa8b-11e6-a095-5254006e85c2</a></p> <p>Another failure on master:</p> <p><a href="https://testing.hpdd.intel.com/test_sets/8e908c38-ac1e-11e6-9116-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/8e908c38-ac1e-11e6-9116-5254006e85c2</a></p> <p>This is causing a lot of test failures.</p> <p>Li Xi, could you please take a look.</p> <p>Li Xi - For sanity test_255b, we are only measuring the total amount of cache and amount of cache used for ost1. Yet, the first thing we do is stripe the file across all OSTs; ‘lfs setstripe –c -1 -i 0 …’. To see the impact of caching on ost1 only, do we want to limit the file to a single ost, in particular ost1, meaning ‘lfs setstripe –c 1 -i 0 ...' ? A file on multiple OSTs (full striping) versus a file on a single OST could change amount of cache used by the willread hint on ost1 when you have more than one OST.</p> <p>Could this explain why this test passes some of the time and fails some of the time?</p> <p>In my testing, using a single striped file for this test succeeds every time and striping a file over 4 OSTs fails every time.</p> <p>James, are the 4 OSTs on the same OSS?</p> <p>If you have a setup that reproduces this issue handy could you try add sync on the line after dd?</p> <p>another on master:<br/> <a href="https://testing.hpdd.intel.com/test_sets/5d201c00-ad94-11e6-8144-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/5d201c00-ad94-11e6-8144-5254006e85c2</a></p> <p>John - I have two OSSs with two OSTs each. </p> <p>Since there is already a sync on ost1 after the write, I'll try the sync on the client.</p> <p>This test still fails with sync after the write. </p> <p>James Nunez (james.a.nunez@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/23867" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/23867</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8738" title="sanity test_255b: FAIL: Ladvise willread should use more memory than 76800 KiB" class="issue-link" data-issue-key="LU-8738"><del>LU-8738</del></a> tests: ladvise dontneed test write to single OST<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 79e15a673e67d80fbf2d04db192a8e14b0802096</p> <p>This looks a must fail test, we'd try to land the fix asap.</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/23867/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/23867/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8738" title="sanity test_255b: FAIL: Ladvise willread should use more memory than 76800 KiB" class="issue-link" data-issue-key="LU-8738"><del>LU-8738</del></a> tests: ladvise dontneed test write to single OST<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: c632d6094c5a228c86c898400192e81b03833fc5</p> <p>Landed for 2.9</p> Development Rank 1|hzysm7: Rank (Obsolete) 9223372036854775807 Severity