[LU-5763] Interop 2.6.0<->2.7 sanity-lfsck test_10: (16) unexpected status

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.6.0, Lustre 2.7.0
• Type: Bug
• Priority: Minor
• Reporter: Maloo
• Assignee: nasf (Inactive)
• Resolution: Duplicate

Environment

server: lustre-master build # 2691
client: 2.6.0

• Severity: 3

Description

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

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/4dc94aa6-5553-11e4-a570-5254006e85c2.

The sub-test test_10 failed with the following error:

(16) unexpected status

test log

CMD: shadow-6vm12 /usr/sbin/lctl get_param -n mdd.lustre-MDT0000.lfsck_namespace
name: lfsck_namespace
magic: 0xa0629d03
version: 2
status: scanning-phase2
flags: scanned-once,inconsistent
param:
time_since_last_completed: 149 seconds
time_since_latest_start: 35 seconds
time_since_last_checkpoint: 4 seconds
latest_start_position: 12, N/A, N/A
last_checkpoint_position: 26129, [0x200000bd1:0x2:0x0], 0x471591dd68dc7bba
first_failure_position: N/A, N/A, N/A
checked_phase1: 15150
checked_phase2: 6572
updated_phase1: 3993
updated_phase2: 5633
failed_phase1: 0
failed_phase2: 0
directories: 1003
dirent_repaired: 0
linkea_repaired: 3993
nlinks_repaired: 0
lost_found: 0
multiple_linked_checked: 5992
multiple_linked_repaired: 1
unknown_inconsistency: 0
unmatched_pairs_repaired: 0
dangling_repaired: 0
success_count: 3
run_time_phase1: 31 seconds
run_time_phase2: 4 seconds
average_speed_phase1: 488 items/sec
average_speed_phase2: 1643 objs/sec
real_time_speed_phase1: N/A
real_time_speed_phase2: 1521 objs/sec
current_position: [0x200000bd0:0x38ba:0x0]
 sanity-lfsck test_10: @@@@@@ FAIL: (16) unexpected status 

Info required for matching: sanity-lfsck 10

Issue Links

• duplicates: LU-5301 Test failure sanity-lfsck test_17: (3...

Comments

[Jodi Levi (Inactive)]

Fan Yong,
Can you comment if this is just a test interop issue? We aren't landing patches on b2_6, so we may just ignore this interop test failure.

[nasf (Inactive)]

There are too much objects left from former other sanity-xxx tests, as to the LFSCK could NOT finish the scanning in the given time. So it is not an interoperability issue, but related with the test environment and test scripts. We have another ticket to adjust the sanity-lfsck test timeout in LU-5301. If we do not want to land patches to b2_6, then we can mark this one as the duplication of LU-5301.

[nasf (Inactive)]

It is another instance of LU-5301.