[LU-1804] Failure sanity-scrub test_9: Unexpected speed 182, should not less than 220

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.3.0, Lustre 2.4.0
• Severity: 3
• Assignee: nasf (Inactive)
• Reporter: Maloo

Description

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

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/9bc93c26-f262-11e1-9def-52540035b04c.

The sub-test test_9 failed with the following error:

(11) Unexpected speed 182, should not less than 220

This is probably due to running in a VM environment, where the whole VM may face CPU/memory/disk contention from other VMs running on the same node. It may be that this test should have a lower threshold when running in a VM?

Info required for matching: sanity-scrub 9

Comments

[nasf (Inactive)]

The patch:

http://review.whamcloud.com/#change,3846

[nasf (Inactive)]

The Maloo test log seems lost.

The OI scrub speed depends on the CPU/RAM schedule, there may be more delay under VM environment. But it is difficult to say which threshold is suitable. So may be we should skip speed related test under VM environment, but it is difficult for the test scripts to detect whether it is tested under VM environment or not. Another possible replacement is that skip OI scrub speed tests under the environment which has less CPU cores or hyper-threads. How do you think?