Have a set of tests run against each file system about crashmonkey HOT 4 CLOSED

1. Test mmap() and file read()/write() at the same time. One process does file IO with read(), write(). Another process does mmap().
2. Test crashes in the middle of rename
3. Truncating a file, then creating another file

from crashmonkey.

4. Allocate resources such as inodes and data blocks until file system is 95% full. Then crash in the middle of workloads which allocate a resource, then deallocate the resource, repeatedly.
5. Modify xfstests for crash testing

from crashmonkey.

For file systems that journal data, we should profile/test workloads where we fill the journal up so that it is forced to write it out

from crashmonkey.

Agreed. In general I think our setup should always push the file system to the brink of resource exhaustion (90% space used, smallest journal possible etc) and then run our tests.

from crashmonkey.