Logging
Fix non-static logMINOR. Oops.
Do loop checking inside onGotKey; this is clearer and allows us to return a slightly more accurate boolean.
Purge false positives log spam. It is not necessary, and not helpful. If the 20%+ "false positives" were the result of actual bloom filter false positives it would indicate a serious problem, but the most likely explanation is simply a consequence of us fetching more blocks than we strictly need (since some of them will fail), and similar issues. We could quantify this in detail but IMHO it isn't a serious problem.
Merge branch 'kill-false-positives-reporting' into split-file-fetcher-storage
Rename, explain a little.
Remove changedSomething flag, unnecessary, all these odd exits we've clearly changed something.
Add a callback for when a segment is restarted due to data corruption.
Re-register on corruption, re-check the datastore.
Add makeRAF() with initial contents to copy to factory.
Factory for PooledRandomAccessFileWrapper's using a FilenameGenerator.
Abstract proxy RAF with ability to switch between implementations.
Make TempBucketFactory able to create LockableRandomAccessThing's (no encryption yet but otherwise works, if there is plenty of RAM we start off as byte array and then moved to disk later).
Use TempBucketFactory for RAFs as well.