[LU-6012] sanity-scrub test_6 test_7 test_8 test_9 test_10a: expected 'inconsistent' but got 'inconsistent,auto'

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.7.0
• Fix Version/s: Lustre 2.7.0
• Type: Bug
• Priority: Blocker
• Reporter: Maloo
• Assignee: nasf (Inactive)
• Resolution: Fixed
• Severity: 3

Description

This issue was created by maloo for Andreas Dilger <[e-mail]>

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/83119ac0-7f6e-11e4-b486-5254006e85c2.

The sub-test test_6 failed with the following error:

(4) Expected 'inconsistent' on mds1, but got 'inconsistent,auto'

I expect that this is some kind of problem introduced by the landing of change http://review.whamcloud.com/12738 "LU-1453 scrub: auto trigger OI scrub more flexible" since the problem appeared for the first time for master on 2014-12-03, the same day that patch landed. There were a couple of related failures on an earlier version of that patch on 2014-11-17 before it landed.

Info required for matching: sanity-scrub 6

Issue Links

• is related to: LU-1453 LFSCK 4: Improve OI scrub trigger str...

Comments

[nasf (Inactive)]

This bug is introduced by the LFSCK 4 patch for LU-1453, since such ticket is NOT closed yet, I prefer to use such ticket (LU-1453) which is in the LFSCK 4 scope.

[nasf (Inactive)]

It will be handled in LU-1453.

[Andreas Dilger]

Is there a plan for fixing this bug? It is causing a large number of test failures.

[Andreas Dilger]

The original failure may be caused by test_5:

Update not seen after 6s: wanted 'crashed' got 'init'
 sanity-scrub test_5: @@@@@@ FAIL: (11) Expected 'crashed' on mds1 

[nasf (Inactive)]

The patch http://review.whamcloud.com/12958 is used for handling such trouble. Let's wait for the latest test result.

[Gerrit Updater]

Fan Yong ([e-mail]) uploaded a new patch: http://review.whamcloud.com/13020
Subject: LU-6012 scrub: NOT miss to auto detect inconsistent OI mapping
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: c284600e214fa0e990486dea404259dd6e721f55

[Andreas Dilger]

This has also shown failures in test_6 with:

fail_loc=0x191
CMD: shadow-16vm12 /usr/sbin/lctl get_param -n osd-ldiskfs.lustre-MDT0000.oi_scrub
/usr/lib64/lustre/tests/sanity-scrub.sh: line 693: N/A + 1: division by 0 (error token is "+ 1")
Error: 'test_6 returned 1'

[nasf (Inactive)]

The "N/A" from OI scrub statistics output is because the last_checkpoint_position is not properly initialised after reset. The patch 13020 has fixed that.

[Gerrit Updater]

Andreas Dilger ([e-mail]) merged in patch http://review.whamcloud.com/13020/
Subject: LU-6012 scrub: NOT miss to auto detect inconsistent OI mapping
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 6b0fa766a4444cf655e965aba067a07143101966

[nasf (Inactive)]

The patch has been landed to master.