So, been doing more analysis of what happened...
suddenly, the database started choking and spitting out errors as fast as
it could write to messages.log (sample errors pasted here)
This continued right up until the partition was filled.
We've never seen this sort of error before in our logs and we have not
figured out what happened to trigger it. (This means we're kinda scared we
will cause it to happen again).
This is the enterprise version (Neo4j - Graph Database Kernel 1.8.M07)