You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2014/06/02 20:40:02 UTC
[jira] [Resolved] (OAK-1869) TarMK: Incorrect tar entry
verification in recovery mode
[ https://issues.apache.org/jira/browse/OAK-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved OAK-1869.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.1
Fixed in revision 1599299.
> TarMK: Incorrect tar entry verification in recovery mode
> --------------------------------------------------------
>
> Key: OAK-1869
> URL: https://issues.apache.org/jira/browse/OAK-1869
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, segmentmk
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Critical
> Fix For: 1.1
>
>
> When recovering segments from a forcibly closed tar file (i.e. one without a proper tar index), the TarMK will scan all tar entries and verify their checksums. Unfortunately that checksum verification is incorrect, which leads to a lot of errors like the one below, and to the affected segments being discarded.
> {noformat}
> Invalid entry checksum at offset NNNNN in tar file /path/to/dataNNNNNNx.tar, skipping...
> {noformat}
> In practice this leads to the TarMK undoing a lot of recent changes until it finds a segment that hasn't been discarded because of such an incorrect checksum verification.
--
This message was sent by Atlassian JIRA
(v6.2#6252)