[LU-17037] Tests should run with high and sparse index numbers for OSTs and MDTs

• Type: Task
• Resolution: Unresolved
• Priority: Minor
• Affects Version/s: Lustre 2.15.3, Lustre 2.17.0
• Labels: tests
• Severity: 4
• Assignee: Jian Yu
• Reporter: Colin Faber

Description

As a long term effort to improve the overall stability of lustre, the test suite should be evaluated and modified to allow for testing against OST and MDT sets which contain index numbers that are both high and sparse.

What I mean by this is that in many cases we're seeing more sites choosing to deploy flash OSTs within the first 100 slots, and then moving all HDD OSTs to index slots > 100 or vice-versa.

This has been shown to introduce issues which some features (most recently a memory corruption issue within pool quotas: LU-17034)

Right now the existing test suite assumes that OSTs will exist on certain low-index numbers which are hard coded into it.

This is sub-optimal to catch cases such as LU-17034, as a result we will need to modify the test suite to allow for testing these cases for all features.

Issue Links

• is related to: LU-19472 sanity test_103b failed with sparse OST indexes
• is related to: LU-17034 memory corruption caused by bug in qmt_seed_glbe_all
• is related to: LU-19471 runtests test_1: FAIL: Space not all freed with sparse OST indexes
• is related to: LU-16331 "lfs find -O UUID" does not match first OST after gap
• is related to: LU-14058 Create tests for large number of MDTs