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-5208 Lustre <p>Running sanity-lfsck with the stated environment, tests 18c, 18d, 18e, and 19a fail and test 19b hangs. Test results are at <a href="https://maloo.whamcloud.com/test_sessions/5ad54b54-f5a5-11e3-b29e-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/5ad54b54-f5a5-11e3-b29e-52540035b04c</a> .</p> <p>sanity-lfsck test 18c fails with the error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>sanity-lfsck test_18c: @@@@@@ FAIL: (4) Expect 3 fixed on mds1, but got: 2 </pre> </div></div> <p>Right before this test fails, the output from /proc/fs/lustre/mdd/scratch-MDT0000/lfsck_layout on mds01, MDT0, is:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>name: lfsck_layout magic: 0xb173ae14 version: 2 status: completed flags: param: all_targets,orphan time_since_last_completed: 2912 seconds time_since_latest_start: 2912 seconds time_since_last_checkpoint: 2912 seconds latest_start_position: 0 last_checkpoint_position: 25098 first_failure_position: 0 success_count: 1 repaired_dangling: 0 repaired_unmatched_pair: 0 repaired_multiple_referenced: 0 repaired_orphan: 2 repaired_inconsistent_owner: 0 repaired_others: 0 skipped: 0 failed_phase1: 0 failed_phase2: 0 checked_phase1: 8 checked_phase2: 2 run_time_phase1: 0 seconds run_time_phase2: 0 seconds average_speed_phase1: 8 items/sec average_speed_phase2: 2 objs/sec real-time_speed_phase1: N/A real-time_speed_phase2: N/A current_position: N/A </pre> </div></div> Lustre 2.5.60 on the OpenSFS cluster, CentOS 6.5 with one server (mds01) with a MGS and MDS with two MDTs, another server (mds02) with MDS and two MDTs, four OSSs with two OSTs each and four clients. LU-5208

sanity-lfsck test_18c failure: Expect 3 fixed on mds1, but got: 2

Bug Minor Resolved Fixed nasf James Nunez lfsck Mon, 16 Jun 2014 22:53:18 +0000 Mon, 25 Aug 2014 23:13:03 +0000 Mon, 25 Aug 2014 23:13:03 +0000 Lustre 2.6.0 Lustre 2.7.0 0 2 <p>Please refer to the comment in the <a href="https://jira.whamcloud.com/browse/LU-5209" title="sanity-lfsck test_18d failure: Expect file2 size 4, but got 0" class="issue-link" data-issue-key="LU-5209"><del>LU-5209</del></a>, we need the LFSCK log to analysis the LFSCK behaviour.</p> <p>sanity-lfsck test logs for 2.6.0-RC1 are at: <a href="https://testing.hpdd.intel.com/test_sessions/5e3c96b0-0c68-11e4-9892-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sessions/5e3c96b0-0c68-11e4-9892-5254006e85c2</a> . </p> <p>Here is the patch:<br/> <a href="http://review.whamcloud.com/#/c/11275/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/11275/</a></p> <p>I tried patch 11275 and the test passes, but the output and the comments don't match. </p> <p>From the output of sanity-lfsck test 18c with this patch:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Trigger layout LFSCK on all devices to find out orphan OST-object Started LFSCK on the device scratch-MDT0000: scrub layout There should be some stub under .lustre/lost+found/MDT0001/ ls: cannot access /lustre/scratch/.lustre/lost+found/MDT0001/*-N-0: No such file or directory There should be some stub under .lustre/lost+found/MDT0000/ 216172799310430210 -r-------- 1 root root 2097152 Aug 4 16:42 /lustre/scratch/.lustre/lost+found/MDT0000/[0x300000401:0x2:0x0]-N-0 216172799310430211 -r-------- 1 root root 2097152 Aug 4 16:42 /lustre/scratch/.lustre/lost+found/MDT0000/[0x300000401:0x3:0x0]-N-0 Resetting fail_loc on all nodes...done. PASS 18c (7s) </pre> </div></div> <p>So, the comment expects something to be in $mount/.lustre/lost+found/scratch-MDT0001, but there is no scratch-MDT0001 subdirectory under lost+found. Maybe with the change in this patch to using "$LFS setstripe -c 1", we shouldn't expect anything there to be an MDT0001 subdirectory?</p> <p>I put some debug prints n the test and there is not scratch-MDT0001 subdirectory:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Trigger layout LFSCK on all devices to find out orphan OST-object Started LFSCK on the device scratch-MDT0000: scrub layout ls -ail /lustre/scratch/.lustre/lost+found/ total 8 144115188109410307 dr-x------ 3 root root 4096 Aug 4 17:37 . 216172799310430209 drwx------ 3 root root 4096 Aug 4 17:38 MDT0000 ls -ail /lustre/scratch/.lustre/lost+found/MDT* total 4104 216172799310430209 drwx------ 3 root root 4096 Aug 4 17:38 . 144115188109410307 dr-x------ 3 root root 4096 Aug 4 17:37 .. 216172799310430210 -r-------- 1 root root 2097152 Aug 4 17:38 [0x300000401:0x2:0x0]-N-0 216172799310430211 -r-------- 1 root root 2097152 Aug 4 17:38 [0x300000401:0x3:0x0]-N-0 There should be some stub under .lustre/lost+found/MDT0001/ ls: cannot access /lustre/scratch/.lustre/lost+found/MDT0001/*-N-0: No such file or directory </pre> </div></div> <p>It is the test scripts issue, the comment should be "There should NOT be some stub under .lustre/lost+found/MDT0001/". I will update the patch.</p> <p>The patch has been landed to master.</p> Related LU-5209 LU-5210 LU-5211 Development Rank 1|hzwp6v: Rank (Obsolete) 14536 Severity