Saving file content with Roundup is not an atomic operation. Thus, there is a small window in which a file exists without being attached to a nodeid in the database.

If the roundup process is killed at that point (say, because the computer crashes), and restarted, its next node created will reference the wrong file.

(For example, if the last stored file was msg10, but roundup's db only knows about msg9, the next file actually created will be msg10.tmp, though roundup will dereference the old msg10 file.

The attached patch attempts to fix this. It contains thorough documentation, including suggestions on how to further enhance the design.

I've applied the patch. There's some issues with the anydbm backend failing unit tests now though.

All unit tests now passing.