Matrix robustness section
From Linux NFS
(Difference between revisions)
(→Resource limit testing) |
(→Resource limit testing) |
||
| Line 95: | Line 95: | ||
<td>III.B.2</td> | <td>III.B.2</td> | ||
<td> | <td> | ||
| - | Test stability of client in out of | + | Test stability of client in out of memory situation</td><td>valgrind</td><td>'''new'''</td><td></td><td>IA32</td> |
| + | </tr> | ||
<tr> | <tr> | ||
<td>III.B.3</td> | <td>III.B.3</td> | ||
<td> | <td> | ||
| - | Test stability of client in out of | + | Test stability of client in out of disk space on server situation</td><td>dd,fsstress</td><td>'''done'''</td><td>BULL</td><td>Simple error message ''no space left on device''</td> |
| - | + | ||
<tr> | <tr> | ||
<td>III.B.4</td> | <td>III.B.4</td> | ||
<td> | <td> | ||
| - | Test stability of client in out of | + | Test stability of client in out of inode situation</td><td></td><td></td><td></td><td></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>III.B.5</td> | <td>III.B.5</td> | ||
<td> | <td> | ||
| - | Test stability of | + | Test stability of client in out of swap space situation</td><td></td><td></td><td></td><td></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>III.B.6</td> | <td>III.B.6</td> | ||
<td> | <td> | ||
| - | Test stability of server in out of | + | Test stability of server in out of pid situation</td><td></td><td></td><td></td><td></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>III.B.7</td> | <td>III.B.7</td> | ||
<td> | <td> | ||
| - | Test stability of server in out of | + | Test stability of server in out of memory situation</td><td>valgrind</td><td>'''new'''</td><td></td><td>IA32</td> |
| + | </tr> | ||
<tr> | <tr> | ||
<td>III.B.8</td> | <td>III.B.8</td> | ||
| + | <td> | ||
| + | Test stability of server in out of disk space situation</td><td>dd,fsstress</td><td>'''done'''</td><td>BULL</td><td> Simple error message ''no space left on device''</td> | ||
| + | <tr> | ||
| + | <td>III.B.9</td> | ||
<td> | <td> | ||
Test stability of server in out of inode situation</td><td></td><td></td><td></td><td></td> | Test stability of server in out of inode situation</td><td></td><td></td><td></td><td></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| - | <td>III.B. | + | <td>III.B.10</td> |
<td> | <td> | ||
Test stability of server in out of swap space situation</td><td></td><td></td><td></td><td></td> | Test stability of server in out of swap space situation</td><td></td><td></td><td></td><td></td> | ||
Revision as of 11:04, 19 May 2005
Section III
Contents |
ROBUSTNESS TESTING
Basic stability assessments
| test | tool test | status | Owner | notes | |
| III.A.1 |
Run iozone for 2 weeks on basic client/server operations, using:
| IOzone | done | BULL | Now testing with fsstress and FFSB |
| III.A.2 |
Run automounter use case for 2 weeks on amd, autofs, and autong, using:
| e.g. Crashme more | New | none | none |
| III.A.3 |
Run NFS server for 2 wks with random configuration changes, using:
| OPEN | OSDL | ||
| III.A.4 |
Run connectathon locking tests against NFS server for 2 weeks, using:
| NEW | |||
| III.A.5 |
Run fsstress 2 weeks on basic client/server operations, using:
| fsstress | Done | BULL | 1 week |
| III.A.6 |
Run FFSB 1 day on basic client/server operations in stress configuration, using:
| ffsb | Done | BULL | 1 day |
Resource limit testing
| test | tool test | status | Owner | notes | |
| III.B.1 | Test stability of client in out of pid situation | ||||
| III.B.2 | Test stability of client in out of memory situation | valgrind | new | IA32 | |
| III.B.3 | Test stability of client in out of disk space on server situation | dd,fsstress | done | BULL | Simple error message no space left on device |
| III.B.4 | Test stability of client in out of inode situation | ||||
| III.B.5 | Test stability of client in out of swap space situation | ||||
| III.B.6 | Test stability of server in out of pid situation | ||||
| III.B.7 | Test stability of server in out of memory situation | valgrind | new | IA32 | |
| III.B.8 | Test stability of server in out of disk space situation | dd,fsstress | done | BULL | Simple error message no space left on device |
| III.B.9 | Test stability of server in out of inode situation | ||||
| III.B.10 | Test stability of server in out of swap space situation |
Stress load testing
- Run LTP NFS fstress in a std config on each release fsx, fsstress (1hour), ffsb (1hour) In Progress
- Analyze load balancing, failure modes, etc. under different stress loads New
- Destructive testing by measuring point of failure for various loads New
Scalability (robustness)
- Find maximum number of connections to Linux IA-32 server Fsstress, fsx New
- Find maximum number of files for Linux IA-32 exported file system Fsstress, fsx
- Find maximum file size on Linux IA-32 Fsstress, fsx New
- Find maximum number of mounted file systems on client Fsstress, fsx New
- Test robustness on NUMA when scaling CPU, mem, NIC, or disk count New
- Test robustness on SMP when scaling CPU, mem, NIC, or disk count New
- Test correctness of NFS client when backed by a large (>100GB) cachefs New
- Find maximum number exported file systems on server New
- Find maximum size of exported file systems on server New
Recovery from problems while under light/normal/heavy loads
- Test short & long term local network failure (unplugged cable, ifdown eth0, etc.) Open OSDL
- Test short & long duration remote network partition Open OSDL
- Test behavior during crash/reboot of server with clients holding various states Open OSDL more
- Test multiple clients using, locking, etc. same files New
- Test behavior of server with failed storage device New
- Test behavior during crash of client with open delegations and locks New
- Test recovery from denied permission New
- Test recovery from JUKEBOX/DELAY New
- Test recovery from ESTALE New
