[LU-5079] conf-sanity test_47 timeout

• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Fix Version/s: Lustre 2.7.0, Lustre 2.5.4
• Affects Version/s: Lustre 2.6.0
• Labels: llnl patch
• Severity: 3
• Assignee: Jian Yu
• Reporter: Maloo

Description

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

This issue relates to the following test suite run:
http://maloo.whamcloud.com/test_sets/7f09a2f6-dd9d-11e3-9262-52540035b04c
https://maloo.whamcloud.com/test_sets/99ea9712-dc88-11e3-9450-52540035b04c

The sub-test test_47 failed with the following error:

test failed to respond and timed out

Info required for matching: conf-sanity 47

Issue Links

• is duplicated by: LU-5773 obdfilter-survey test 1c: oom occurred on OSS
• is related to: LU-5077 insanity test_1: out of memory on MDT in crypto_create_tfm()
• is related to: LU-5900 replay-dual test_11: rm: cannot remove `/mnt/lustre/f11.replay-dual-[1-5]': No such file or directory
• is related to: LU-5901 replay-dual test_15a: import is not in FULL state
• is related to: LU-5902 replay-dual test_20: FAIL: recovery time is growing 215 > 107
• is related to: LU-5803 This server is not able to keep up with request traffic
• is related to: LU-5724 IR recovery doesn't behave properly with Lustre 2.5
• is related to: LU-5077 insanity test_1: out of memory on MDT in crypto_create_tfm()
• is related to: LU-5805 tgt_recov blocked and "waking for gap in transno"
• is related to: LU-4578 Early replies do not honor at_max
• is related to: LU-5358 Failure on test suite replay-vbr test_7e

Comments

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch http://review.whamcloud.com/12714/
Subject: LU-5079 tests: fix service_time in max_recovery_time()
Project: fs/lustre-release
Branch: b2_5
Current Patch Set:
Commit: 4e8def3e32ad76808a5b8336d43430a5318e20aa

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch http://review.whamcloud.com/12724/
Subject: LU-5079 tests: fix service_time in max_recovery_time()
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 9bb24bf1ce4977b32d4bf9b55cef5a25072cef5e

[Gerrit Updater]

Jian Yu ([e-mail]) uploaded a new patch: http://review.whamcloud.com/12724
Subject: LU-5079 tests: fix service_time in max_recovery_time()
Project: fs/lustre-release
Branch: master
Current Patch Set: 3
Commit: 1c58e970d684edfefba3725f869ffd36c6a4475e

[Jian Yu]

Test results showed that by increasing the time in max_recovery_time() in test framework, the failures in LU-5900 and LU-5901 were resolved. And by adding some margin into the recovery time comparison condition, the failure in LU-5902 was resolved.

[Gerrit Updater]

Jian Yu ([e-mail]) uploaded a new patch: http://review.whamcloud.com/12724
Subject: LU-5079 tests: fix service_time in max_recovery_time()
Project: fs/lustre-release
Branch: master
Current Patch Set: 2
Commit: 4c0c53265dc9fb17bb8999548d656103ced58928

[Gerrit Updater]

Jian Yu ([e-mail]) uploaded a new patch: http://review.whamcloud.com/12714
Subject: LU-5079 tests: fix service_time in max_recovery_time()
Project: fs/lustre-release
Branch: b2_5
Current Patch Set: 3
Commit: 264ea0643d46240b8b45dd673aeff3b4fe76bd10

[Jian Yu]

I just pushed a patch to Lustre b2_5 branch to fix the calculation of of service_time in max_recovery_time(): http://review.whamcloud.com/12714.
I'll check the test results.

[Andreas Dilger]

Alexander, could you please take a look at LU-5900, LU-5901, LU-5902 failures? This looks to be caused by the http://review.whamcloud.com/11213 patch backported to b2_5 (http://review.whamcloud.com/12365). Is this something that is just causing the tests to fail that won't affect real users, or is there something bad in b2_5 that will cause recovery problems for users also?

[Jian Yu]

The patches caused regression failures LU-5900, LU-5901 and LU-5902 on master and b2_5 branches.

[Peter Jones]

It has landed to master now