[LU-5788] recovery-double-scale test_pairwise_fail: no enough free disk space

• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Fix Version/s: Lustre 2.10.0
• Affects Version/s: Lustre 2.7.0, Lustre 2.10.0
• Environment: server and client lustre-master build #2690; client is running SLES11 SP3
• Severity: 3
• Assignee: Hongchao Zhang
• Reporter: Maloo

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/65fa24d0-565a-11e4-97f1-5254006e85c2.

The sub-test test_pairwise_fail failed with the following error:

test_pairwise_fail returned 1

+ echoerr 'no enough free disk space: need 15768, avail 0'
+ echo 'no enough free disk space: need 15768, avail 0'
no enough free disk space: need 15768, avail 0
++ hostname

Info required for matching: recovery-double-scale pairwise_fail

Issue Links

• is related to: LU-8544 recovery-double-scale test_pairwise_fail: start client on trevis-54vm5 failed
• is related to: LU-9365 Sync data before get df data

Comments

[Peter Jones]

Landed for 2.10

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/26031/
Subject: LU-5788 test: fix the cmd to getfree space
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 349d0de314522868105a6deabc73d8c2410abc0f

[Gerrit Updater]

Hongchao Zhang ([e-mail]) uploaded a new patch: https://review.whamcloud.com/26031
Subject: LU-5788 test: fix the cmd to getfree space
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: f0b6c1d6c182d525bb7a138a6ed78bbdb38b43f0

[Gerrit Updater]

Hongchao Zhang ([e-mail]) uploaded a new patch: http://review.whamcloud.com/23787
Subject: LU-5788 test: debug log
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 514770567ec6d1139faca6ed403f7483d42b0882

[Andreas Dilger]

It seems that this is a problem in the test scripts (e.g. test loads are using more space than available in the filesystem, or not deleting old files?). It would be useful, at a minimum, to print the lfs df output at the start and at least basic information about how much space is being used by the "dd" load each time.