Details
-
Bug
-
Resolution: Fixed
-
Major
-
Lustre 2.11.0
-
None
-
Trevis2, full
server: RHEL 7.3, ldiskfs, branch master, v2.10.51, b3620
client: RHEL 7.3, branch master, v2.10.51, b3620
-
3
-
9223372036854775807
Description
https://testing.hpdd.intel.com/test_sessions/9b7c7e8e-7b5a-4f4d-af09-400c586a8340
This issue looks like LU-3801, but it failed with an I/O error rather than no space.
From test_log:
write/read 30 MB file Warning: can't complete test: can't sync bigfile21643: No space left on device special tests failed parallel-scale-nfsv3 test_connectathon: @@@@@@ FAIL: connectathon failed: 1 Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:4980:error() = /usr/lib64/lustre/tests/functions.sh:548:run_connectathon() = /usr/lib64/lustre/tests/parallel-scale-nfs.sh:108:test_connectathon() = /usr/lib64/lustre/tests/test-framework.sh:5256:run_one() = /usr/lib64/lustre/tests/test-framework.sh:5295:run_one_logged() = /usr/lib64/lustre/tests/test-framework.sh:5142:run_test() = /usr/lib64/lustre/tests/parallel-scale-nfs.sh:110:main()
Attachments
Issue Links
- is related to
-
LU-10689 parallel-scale-nfsv3 test_connectathon: can't sync bigfile21829: File too large
-
- Open
-
-
LU-4905 2.1.6<->2.4.3 interop: parallel-scale-nfsv3 test connectathon: No space left on device
-
- Resolved
-
- mentioned in
-
Page No Confluence page found with the given URL.
-
Page No Confluence page found with the given URL.
-
Page No Confluence page found with the given URL.
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
I was trying to find the maximum file system size that connectathon would fail with the ‘No space left on device’ error when running the “special” test type. Looking at the connectathon code, it looks like the “bigfile” test should take the most space on the file system by creating a 30M file. So, I started running parallel-scale-nfsv3 on smaller and smaller file systems until I got the ‘no space’ error.
At ~96 MB (100925440 bytes) file system, I was able to get on run of parallel-scale-nfsv3 to fail with the no space error, but seven other runs with the same file system ran to completion. So I printed out the amount of free space on the file system before and after each of the connectathon tests, basic (-b), general (-g), special (-s), and lock (–l).
For a test run that succeeded, here’s the memory before and after 10 iterations of each test type:
Before –b tests Free space: 100925440 bytes
After –b tests Free space: 96731136 bytes
Before –g tests Free space: 96731136 bytes
After –g tests Free space: 97255424 bytes
Before –s tests Free space: 97255424 bytes
After –s tests Free space: 99090432 bytes
Before –l tests Free space: 99090432 bytes
After –l tests Free space: 100401152 bytes
Another run that succeeded:
Before –b tests Free space: 100925440 bytes
After –b tests Free space: 94371840 bytes
Before –g tests Free space: 94371840 bytes
After –g tests Free space: 95158272 bytes
Before –s tests Free space: 95158272 bytes
After –s tests Free space: 49807360 bytes
Before –l tests Free space: 49807360 bytes
After –l tests Free space: 100401152 bytes
For a test run that fails in the special test type with the no space error, we see
Before –b tests Free space: 100925440 bytes
After –b tests Free space: 94371840 bytes
Before –g tests Free space: 94371840 bytes
After –g tests Free space: 97255424 bytes
Before –s tests Free space: 97255424 bytes
[Experienced 'no space' failure in –s tests]
After –s tests Free space: 81264640 bytes