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-4806 Lustre <p>This issue was created by maloo for Nathaniel Clark &lt;nathaniel.l.clark@intel.com&gt;</p> <p>This issue relates to the following test suite run:<br/> <a href="http://testing.hpdd.intel.com/test_sets/963b13e0-b144-11e3-808b-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://testing.hpdd.intel.com/test_sets/963b13e0-b144-11e3-808b-52540035b04c</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/bcc5032e-b147-11e3-98c2-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/bcc5032e-b147-11e3-98c2-52540035b04c</a></p> <p>The sub-test test_53 failed with the following error:</p> <blockquote> <p>can not match last_seq/last_id for &#42;OST&#42;-osc-MDT0000</p></blockquote> <p>Info required for matching: sanity 53</p> LU-4806

Test failure sanity test_53: can not match last_seq/last_id for *OST*-osc-MDT0000

Bug Minor Open Unresolved WC Triage Maloo Mon, 24 Mar 2014 15:44:43 +0000 Tue, 19 Apr 2022 16:11:21 +0000 Lustre 2.6.0 Lustre 2.8.0 Lustre 2.10.1 0 8 <p>This is a regression from unlanded patch in <a href="http://review.whamcloud.com/#/c/7936/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/7936/</a></p> <p>Yes, This issue really cause by lprocfs patch. I am also hit it in my local test(<a href="#comment-78888" target="_blank" rel="noopener">comment-78888</a>). I have commented in relate patches for the root cause.</p> <p>I have been looking into it. I see what you mean about not freeing type-&gt;typ_procsym when creating a symlink fails to create. This is only done in the case of proc subdirectories like target_obds. I'm thinking the safest place to free type-&gt;typ_procsym is in class_unregister_type. I testing new patches.</p> <p>The latest <a href="https://jira.whamcloud.com/browse/LU-3319" title="Adapt to 3.10 upstream kernel proc_dir_entry change" class="issue-link" data-issue-key="LU-3319"><del>LU-3319</del></a> patches seem to calm these problems down.</p> <p>Hit this error in rolling upgrade test, after upgrade server from 2.5.2 ldiskfs to b2_6-rc2, clients are still 2.5.2, sanity test_53 failed as the same error.</p> <p>Do we still see this problem anymore? If not we can close this ticket.</p> <p>We're seeing this test failure for 2.7.0. </p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>(debug.c:345:libcfs_debug_mark_buffer()) DEBUG MARKER: sanity test_53: @@@@@@ FAIL: can not match last_seq/last_id for *OST*-osc </pre> </div></div> <p>hit in interop testing with master server(DNE) and 2.5.3 client:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>== sanity test 53: verify that MDS and OSTs agree on pre-creation ====== 19:53:08 (1441075988) Lustre: DEBUG MARKER: == sanity test 53: verify that MDS and OSTs agree on pre-creation ====== 19:53:08 (1441075988) onyx-25: error: get_param: osc/*OST*-osc-/prealloc_last_id: Found no match sanity test_53: @@@@@@ FAIL: can not match last_seq/last_id for *OST*-osc- Lustre: DEBUG MARKER: sanity test_53: @@@@@@ FAIL: can not match last_seq/last_id for *OST*-osc- Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:4343:error_noexit() = /usr/lib64/lustre/tests/test-framework.sh:4374:error() = sanity.sh:3968:test_53() = /usr/lib64/lustre/tests/test-framework.sh:4613:run_one() = /usr/lib64/lustre/tests/test-framework.sh:4648:run_one_logged() = /usr/lib64/lustre/tests/test-framework.sh:4516:run_test() = sanity.sh:3971:main() Dumping lctl log to /home/w3liu/toro_home/test_logs/sanity.test_53.*.1441075990.log FAIL 53 (9s) </pre> </div></div> <p>I see what the problem is. The param "osc/&#42;OST&#42;&#45;osc&#45;/prealloc_last_id" needs to be "osc/&#42;OST&#42;&#45;osc&#45;&#42;/prealloc_last_id". The bug is in get_mdtosc_proc_path() in test-framework.sh. </p> <p>The mdt_index variable is coming back null.</p> <p><a href="https://testing.hpdd.intel.com/test_sets/173b63f6-b575-11e5-bf32-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/173b63f6-b575-11e5-bf32-5254006e85c2</a></p> <p>server: lustre-master #3297 RHEL7 DNE(4 MDT)<br/> client: 2.7.1</p> <p><a href="https://testing.hpdd.intel.com/test_sets/806257c8-a212-11e7-b778-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/806257c8-a212-11e7-b778-5254006e85c2</a> 2.10.1 MOFED zfs</p> <p>James, I see you identified the problem in your Aug'17 comment, could you please make a patch for this?</p> <p>I've looked at sanity test_53 failures for the past year in Maloo for autotest results. For both master and b2_10, this test has not failed with the 'can not match last_seq/last_id for <b>OST</b><del>osc</del>' error this year. I did not look at other branches.</p> <p>We do see this test fail with this error when we’re doing manual testing with all servers on a single node. Here are two examples:<br/> <a href="https://testing.hpdd.intel.com/test_sessions/802c5d30-a212-11e7-b778-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sessions/802c5d30-a212-11e7-b778-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sessions/128214f8-a7c8-11e7-b786-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sessions/128214f8-a7c8-11e7-b786-5254006e85c2</a></p> Development Rank 1|hzwi7b: Rank (Obsolete) 13221 Severity