[LU-10732] sanity-lfsck test_9a: FAIL: (7) Failed to get expected 'completed'

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.12.0
• Affects Version/s: Lustre 2.11.0
• Labels: zfs
• Environment: FSTYPE=zfs
• Severity: 3
• Assignee: Alex Zhuravlev
• Reporter: Jian Yu

Description

sanity-lfsck test_9a - (7) Failed to get expected 'completed'
^^^^^^^^^^^^^ DO NOT REMOVE LINE ABOVE ^^^^^^^^^^^^^

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

This issue relates to the following test suite run:

test_9a failed with the following error:

Update not seen after 30s: wanted 'completed' got 'scanning-phase2'
(7) Failed to get expected 'completed'

Maloo reports:
https://testing.hpdd.intel.com/test_sets/9b5dd5d6-1bc3-11e8-a7cd-52540065bddc
https://testing.hpdd.intel.com/test_sets/2bcb4f88-1bdb-11e8-bd00-52540065bddc
https://testing.hpdd.intel.com/test_sets/a1a3d500-1bd5-11e8-a10a-52540065bddc

Issue Links

• is related to: LU-8856 ZFS-MDT 100% full. Cannot delete files.

Comments

[Peter Jones]

Landed for 2.12

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/31488/
Subject: LU-10732 tests: sanity-lfsck to reset speed limit
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 08342ffa94f559a767c9affbad75440edb6ba024

[Alex Zhuravlev]

https://review.whamcloud.com/#/c/31488/ – this helped me locally, but not sure about autotest..

[nasf (Inactive)]

The logs show that the layout LFSCK on the OST ran very slowly, as to the LFSCK engine on the MDT had to wait for the OST when move to the 2nd phase scanning. But the test scripts does NOT set speed limitation on the OST. And this trouble only happened on the ZFS-based backend.

[Bob Glossman (Inactive)]

another on master:
https://testing.hpdd.intel.com/test_sets/dea2fe62-1bfe-11e8-a7cd-52540065bddc

[Alex Zhuravlev]

https://testing.hpdd.intel.com/sub_tests/query?utf8=✓&test_set%5Btest_set_script_id%5D=4f25830c-64fe-11e2-bfb2-52540035b04c&sub_test%5Bsub_test_script_id%5D=52f5ae12-64fe-11e2-bfb2-52540035b04c&status%5B%5D=FAIL&query_bugs=&warn%5Bnotice%5D=false&builds=&hosts=&gerrit=&test_session%5Btest_group%5D%5B%5D=&test_session%5Buser_id%5D%5B%5D=&test_session%5Bquery_recent_period%5D=2332800&test_session%5Bstart_date%5D=&test_session%5Bend_date%5D=&test_node%5Bos_type_id%5D=&test_node%5Bdistribution_type_id%5D=&test_node%5Barchitecture_type_id%5D=&test_node%5Bfile_system_type_id%5D=&test_node%5Blustre_branch_id%5D=&test_node_network%5Bnetwork_type_id%5D=&commit=Update+results&num_results=50

it's been failing long before that patch.

[Alex Zhuravlev]

I just tried locally w/o LU-8856:
sanity-lfsck test_9a: @@@@@@ FAIL: (7) Failed to get expected 'completed'

[Peter Jones]

Seems to be due to the LU-8856 landing and so that has been reverted

[Jian Yu]

The failure occurred about 7 times in last 3 days, which is affecting patch testing on master branch.