Is there a way to fix Prefix/suffix length inconsistency error?

EventStoreDB
1

I get the following error message:

[PID:02452:014 2015.10.12 14:02:02.337 FATAL StorageChaser ] Error in StorageChaser. Terminating…

System.Exception: Prefix/suffix length inconsistency: prefix length(16727) != suffix length (0).

Actual pre-position: 108471848. Something is seriously wrong in chunk #42-42 (chunk-000042.000000).

at EventStore.Core.TransactionLog.Chunks.TFChunk.TFChunk.TFChunkReadSide.TryReadForwardInternal(ReaderWorkItem workItem, Int64 actualPosition, Int32& length, LogRecord& record) in c:\buildAgent\work\47590a33512c319d\src\EventStore.Core\TransactionLog\Chunks\TFChunk\TFChunkReadSide.cs:line 484

at EventStore.Core.TransactionLog.Chunks.TFChunk.TFChunk.TFChunkReadSideUnscavenged.TryReadClosestForward(Int64 logicalPosition) in c:\buildAgent\work\47590a33512c319d\src\EventStore.Core\TransactionLog\Chunks\TFChunk\TFChunkReadSide.cs:line 82

at EventStore.Core.TransactionLog.Chunks.TFChunkReader.TryReadNextInternal(Int32 retries) in c:\buildAgent\work\47590a33512c319d\src\EventStore.Core\TransactionLog\Chunks\TFChunkReader.cs:line 57

at EventStore.Core.TransactionLog.Chunks.TFChunkChaser.TryReadNext() in c:\buildAgent\work\47590a33512c319d\src\EventStore.Core\TransactionLog\Chunks\TFChunkChaser.cs:line 39

at EventStore.Core.Services.Storage.StorageChaser.ChaserIteration() in c:\buildAgent\work\47590a33512c319d\src\EventStore.Core\Services\Storage\StorageChaser.cs:line 135

at EventStore.Core.Services.Storage.StorageChaser.ChaseTransactionLog() in c:\buildAgent\work\47590a33512c319d\src\EventStore.Core\Services\Storage\StorageChaser.cs:line 107

[PID:02452:014 2015.10.12 14:02:02.610 ERROR Application ] Exiting with exit code: 1.

Exit reason: Error in StorageChaser. Terminating…

Error: Prefix/suffix length inconsistency: prefix length(16727) != suffix length (0).

Actual pre-position: 108471848. Something is seriously wrong in chunk #42-42 (chunk-000042.000000).

It’s not our produciton environment, but I would still like to know what to do if it happens in production. Also, how can this happen and how to recover?

2

So this is totally unheard of?

3

usually this is a corrupt chunk which can be caused for many reasons.

4

Is there anything one can do when this occur?

5

It depends entirely on the reason. The most common is things like
windows disk caching enabled on the machine and a hard shut down in
which case no.