The file system test is one that EROS is not currently doing well on. In the original design, every file was a process. This involved a lot of receive buffer space overhead, so I moved to a design in which there is a single ``file server'' that exports many file objects.

The resulting implementation is based directly on the UNIX indirection block ideas, and uses a 1k block size. I also borrowed some ideas from the WAFL file system (Network Appliance) to simplify growing the inode table.

This test case proved to be a nice validation of the use of persistence. Writing (and rewriting), debugging, and testing the file system implementation took a grand total of two days.