Whamcloud Community JIRA https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 [LU-3246] fc18: sanity test_133c: @@@@@@ FAIL: The counter for destroy on ost was not incremented https://jira.whamcloud.com/browse/LU-3246 Lustre <p>== sanity test 133c: Verifying OST stats ============================================================= 17:23:17 (1366935797)<br/> CMD: client-27vm7 lctl set_param -n osd*.<b>MD</b>.force_sync 1<br/> CMD: client-27vm7 lctl get_param -n osc.<b>MDT</b>.sync_*<br/> CMD: client-27vm7 lctl get_param -n osc.<b>MDT</b>.sync_*<br/> CMD: client-27vm7 lctl get_param -n osc.<b>MDT</b>.sync_*<br/> CMD: client-27vm7 lctl get_param -n osc.<b>MDT</b>.sync_*<br/> CMD: client-27vm7 lctl get_param -n osc.<b>MDT</b>.sync_*<br/> CMD: client-27vm7 lctl get_param -n osc.<b>MDT</b>.sync_*<br/> Waiting for local destroys to complete<br/> CMD: client-27vm7 /usr/sbin/lctl set_param mdt.*.md_stats=clear<br/> mdt.lustre-MDT0000.md_stats=clear<br/> CMD: client-27vm8 /usr/sbin/lctl set_param obdfilter.*.stats=clear<br/> obdfilter.lustre-OST0000.stats=clear<br/> obdfilter.lustre-OST0001.stats=clear<br/> obdfilter.lustre-OST0002.stats=clear<br/> obdfilter.lustre-OST0003.stats=clear<br/> obdfilter.lustre-OST0004.stats=clear<br/> obdfilter.lustre-OST0005.stats=clear<br/> obdfilter.lustre-OST0006.stats=clear<br/> 1+0 records in<br/> 1+0 records out<br/> 524288 bytes (524 kB) copied, 0.00290828 s, 180 MB/s<br/> CMD: client-27vm8 /usr/sbin/lctl get_param obdfilter.lustre-OST0000.stats<br/> write_bytes 1 samples <span class="error">&#91;bytes&#93;</span> 524288 524288 524288<br/> 1+0 records in<br/> 1+0 records out<br/> 1024 bytes (1.0 kB) copied, 0.0022926 s, 447 kB/s<br/> CMD: client-27vm8 /usr/sbin/lctl get_param obdfilter.lustre-OST0000.stats<br/> read_bytes 1 samples <span class="error">&#91;bytes&#93;</span> 4096 4096 4096<br/> CMD: client-27vm8 /usr/sbin/lctl get_param obdfilter.lustre-OST0000.stats<br/> punch 1 samples <span class="error">&#91;reqs&#93;</span><br/> Waiting for local destroys to complete<br/> CMD: client-27vm8 /usr/sbin/lctl get_param obdfilter.lustre-OST0000.stats</p> <p> sanity test_133c: @@@@@@ FAIL: The counter for destroy on ost was not incremented <br/> Trace dump:<br/> = /usr/lib64/lustre/tests/test-framework.sh:4024:error_noexit()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4047:error()<br/> = /usr/lib64/lustre/tests/sanity.sh:8163:check_stats()<br/> = /usr/lib64/lustre/tests/sanity.sh:8274:test_133c()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4301:run_one()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4334:run_one_logged()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4189:run_test()<br/> = /usr/lib64/lustre/tests/sanity.sh:8278:main()<br/> Dumping lctl log to /logdir/test_logs/2013-04-25/lustre-reviews-el6-x86_64-vs-lustre-reviews-fc18-x86_64-<del>full</del>-2_4_1_<em>15112</em>_-70194508889820-153004/sanity.test_133c.*.1366935807.log<br/> CMD: client-27vm1,client-27vm2.lab.whamcloud.com,client-27vm7,client-27vm8 /usr/sbin/lctl dk &gt; /logdir/test_logs/2013-04-25/lustre-reviews-el6-x86_64-vs-lustre-reviews-fc18-x86_64-<del>full</del>-2_4_1_<em>15112</em>_-70194508889820-153004/sanity.test_133c.debug_log.\$(hostname -s).1366935807.log;<br/> dmesg &gt; /logdir/test_logs/2013-04-25/lustre-reviews-el6-x86_64-vs-lustre-reviews-fc18-x86_64-<del>full</del>-2_4_1_<em>15112</em>_-70194508889820-153004/sanity.test_133c.dmesg.\$(hostname -s).1366935807.log</p> <a href="https://maloo.whamcloud.com/test_sets/f457225a-aec7-11e2-a127-52540035b04c">https://maloo.whamcloud.com/test_sets/f457225a-aec7-11e2-a127-52540035b04c</a> LU-3246 fc18: sanity test_133c: @@@@@@ FAIL: The counter for destroy on ost was not incremented Bug Major Resolved Cannot Reproduce WC Triage Minh Diep Tue, 30 Apr 2013 15:25:21 +0000 Wed, 5 Aug 2015 16:23:07 +0000 Wed, 5 Aug 2015 16:23:06 +0000 Lustre 2.4.0 Lustre 2.4.1 0 9 <p>Hit similar issue when testing interop between 2.3.0 client and 2.4 server:<br/> <a href="https://maloo.whamcloud.com/test_sets/e89c3aac-bbee-11e2-b013-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/e89c3aac-bbee-11e2-b013-52540035b04c</a></p> <p>Lustre Branch: b2_4<br/> Lustre Build: <a href="http://build.whamcloud.com/job/lustre-b2_4/27/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_4/27/</a><br/> Distro/Arch: RHEL6.4/x86_64 + FC18/x86_64 (Server + Client)</p> <p>The failure occurred regularly on Lustre b2_4 branch on FC18 client:<br/> <a href="https://maloo.whamcloud.com/test_sets/996b2278-fd79-11e2-9fdb-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/996b2278-fd79-11e2-9fdb-52540035b04c</a></p> <p>Lustre client: <a href="http://build.whamcloud.com/job/lustre-b2_3/41/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_3/41/</a> (2.3.0)<br/> Lustre server: <a href="http://build.whamcloud.com/job/lustre-b2_4/44/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_4/44/</a> (2.4.1 RC1)</p> <p>sanity test 133c hit the same failure:<br/> <a href="https://maloo.whamcloud.com/test_sets/cde5bab8-14f3-11e3-9828-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/cde5bab8-14f3-11e3-9828-52540035b04c</a></p> <p>Lustre build: <a href="http://build.whamcloud.com/job/lustre-b2_4/44/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_4/44/</a> (2.4.1 RC1)<br/> Distro/Arch: RHEL6.4/x86_64 + FC18/x86_64 (Server + Client)</p> <p>sanity test 133c hit the same failure:<br/> <a href="https://maloo.whamcloud.com/test_sets/0cbde1d0-14ee-11e3-ac48-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/0cbde1d0-14ee-11e3-ac48-52540035b04c</a></p> <p>Lustre client: <a href="http://build.whamcloud.com/job/lustre-b2_3/41/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_3/41/</a> (2.3.0)<br/> Lustre server: <a href="http://build.whamcloud.com/job/lustre-b2_4/69/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_4/69/</a> (2.4.2 RC1)</p> <p>sanity test 133c hit the same failure:<br/> <a href="https://maloo.whamcloud.com/test_sets/3c82ea6e-685e-11e3-a16f-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/3c82ea6e-685e-11e3-a16f-52540035b04c</a></p> <p>This has suddenly started to be hit very often on master.</p> <p>Its due to patch 8029 landing. I'm looking at a fix.</p> <p>James,<br/> Have you had a chance to make any progress on this one?</p> <p>We are seeing this failing less than 2% of the time, so reducing from blocker.</p> <p>Is this showing up anymore? Can we close it.</p> <p>This is an old ticket that can be closed.</p> <p>ok</p> Related LU-4513 Development Rank 1|hzvpqn: Rank (Obsolete) 8033 Severity