| ID
| test
| tool test
| status
| owner
| notes
|
| III.A.1
| Run iozone for 2 weeks on basic client/server operations, using:
- Both data and metadata options
- Cached and direct I/O
- Various mount options
| 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:
- Large number of maps
- Randomly mount and run workloads on an automounted partition
- use a variety of workloads, such as randomly chosen fs tests
| e.g. Crashme more
| New
|
|
|
| III.A.3
| Run NFS server for 2 wks with random configuration changes, using:
- Interrupt server in various ways (reboot, power cycle, lan fail)
- Change/reexport export rules at random
- Trigger a client workload at arbitrary times
- Analyze client recovery behaviors
|
| OPEN
| OSDL
|
|
| III.A.4
| Run connectathon locking tests against NFS server for 2 weeks, using:
- Multiple client machines
- Reboot at random
- Analyze client cache coherency behaviors
- Analyze locking behaviors
|
| NEW
|
|
|
| III.A.5
| Run fsstress 2 weeks on basic client/server operations, using:
- Long list random operations (1000 operations)
- hight number of process (100)
| fsstress
| DONE
| BULL
| 1 week
|
| III.A.6
| Run FFSB 1 day on basic client/server operations in stress configuration, using:
- 1 200 000 files
- 100 directories
| ffsb
| DONE
| BULL
| 1 day
|
| ID
| 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
|
|
|
| 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
|
|
|
| III.B.8
| Test stability of server in out of disk space
| 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
|
|
|
|
|
| ID
| test
| tool test
| status
| owner
| notes
|
| III.D.1
| Find maximum number of connections to Linux IA-32 server
| Fsstress, fsx
| New
| Bull (partial)
|
|
| III.D.2
| Find maximum number of files for Linux IA-32 exported file system
| ffsb
| New
|
|
|
| III.D.3
| Find maximum file size on Linux IA-32
|
| New
|
|
|
| III.D.4
| Find maximum number of mounted file systems on client
| Fsstress, fsx
| New
| Bull
|
|
| III.D.5
| Test robustness on NUMA when scaling CPU, mem, NIC, or disk count
| Fsstress, fsx
| New
|
|
|
| III.D.6
| Test robustness on SMP when scaling CPU, mem, NIC, or disk count
| Fsstress, fsx
| New
| Bull (partial)
|
|
| III.D.7
| Test correctness of NFS client when backed by a large (>100GB) cachefs
|
| New
|
|
|
| III.D.8
| Find maximum number exported file systems on server
|
| New
|
|
|
| III.D.9
| Find maximum size of exported file systems on server
|
| New
|
|
|
|
test |
tool test |
status |
Owner |
notes |
| III.E.1 |
Test short & long term local network failure (unplugged cable, ifdown eth0, etc.) | | Open | OSDL | |
| III.E.2 |
Test short & long duration remote network partition | | Open | OSDL | |
| III.E.3 |
Test behavior during crash/reboot of server with clients holding various states | | Open | OSDL | more |
| III.E.4 |
Test multiple clients using, locking, etc. same files | | New | | |
| III.E.5 |
Test behavior of server with failed storage device | | New | | |
| III.E.6 |
Test behavior during crash of client with open delegations and locks | | New | | |
| III.E.7 |
Test recovery from denied permission | | New | | |
| III.E.5 |
Test recovery from JUKEBOX/DELAY | | New | | |
| III.E.5 |
Test recovery from ESTALE | | New | | |
