Test demonstrating that objects can not be written if a bad CRC is encountered in Bitcask
Merge branch 'master' into bitcask-badcrc-eunit-test

Preparing to bring the bad crc unit test into the present
Write even on bitcask bad_crc read

Fixes issue #385
Reads on corrupted files return a bad_crc error, which were not handled.
When writing, if a bad_crc was encountered on read of an existing key,
the write failed. Files being erased, or even truncated were handled
and the write proceeds, but bit corruption would die. I don't think
there is any benefit to the different handling.
Whitespace change to trigger Travis
Adding bad_crc specifically on read before write

Although plenty of other situations may arise where an error upon
reading should simply allow the write to happen, we're going to wait to
standardize backend responses properly before trying to fix those.
This is just to be prudent until the consequences of doing that are
better understood. This makes the fix specific to bitcask bad CRC
errors and nothing more.
Standardization will hopefully happen in issue #496
Add partition to bad bitcask CRC err msg

Also, changed comment on bad CRC unit test to show it is verifying the
fix. The old language was written by the person first showing the
problem existed (Dan R.).
Merge pull request #385 from basho/eas-handle-bitcask-bad-crc

Objects cannot be updated if a bad CRC is encountered by Bitcask