The log block manager currently may leave null bytes at the end of the metadata log file if there is a system crash in the middle of a write. The log block manager should detect null bytes at the end of a metadata entry on startup and potentially truncate the entry or close the container.
Currently, it prints an error along the following lines:
At the time of writing, the workaround for this issue is to truncate the affected file at the start of the incomplete entry in the file. While this may leave orphaned blocks, this should be safe because if the metadata entry was never successfully written then it should not have been considered durable, either.