Running out of disk space ends process and corrupts store.

[evoskuil]

Because there are multiple independent files a lack of disk space on one cannot gracefully suspend a write. The other file may have been written, resulting in an inconsistency. As a result, when growth fails the process terminates and the store is left marked as corrupted. Cross-file write atomicity may be a performance hit that we don't want to accept. But this issue should be managed more gracefully.

[evoskuil]

Mitigated somewhat by configurable file size minimums.

[evoskuil]

Mitigated by existence of live snapshotting in current builds of v4.