Comment 7 for bug 1062969

The implementation of testFileSizeLimit can be much better. The current implementation (now in 2016) requires 4x the max_file_size (minus 111 bytes) to be fallocat'able on your drives. Sure, sure, just turn off fallocate, but that just hides the issue, and fallocate should be on in prod, so it should be on in dev (IMO).

testFileSizeLimit should be changed so that the successfully created large objects are deleted right after that part of the test passes.

I ran in to this when testing with an 8GB drive and a 2GB max_file_size.