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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2016/03/24 00:45:25 UTC

[jira] [Comment Edited] (OAK-4147) TarReader#loadGraph wrongly detects segment graph as corrupt

    [ https://issues.apache.org/jira/browse/OAK-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209438#comment-15209438 ] 

Michael Dürig edited comment on OAK-4147 at 3/23/16 11:45 PM:
--------------------------------------------------------------

The problem seems to be that the calculation of the position of the graph in the tar file uses the raw size of the index for offsetting instead of also including the header (16 bytes) of the index. See patch. 

Will try to come up with a unit test to guard against regressions. 

[~frm] FYI


was (Author: mduerig):
The problem seems to be that the calculation of the position of the graph in the file uses the raw size of the index as for offsetting instead of also including the header (16 bytes) of the index. See patch. 

Will try to come up with a unit test to guard against regressions. 

[~frm] FYI

> TarReader#loadGraph wrongly detects segment graph as corrupt 
> -------------------------------------------------------------
>
>                 Key: OAK-4147
>                 URL: https://issues.apache.org/jira/browse/OAK-4147
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segmentmk
>            Reporter: Michael Dürig
>              Labels: cleanup, gc
>         Attachments: OAK-4147.patch
>
>
> {{org.apache.jackrabbit.oak.plugins.segment.file.TarReader#loadGraph}} sometimes detects a segment graph as corrupt although it isn't. This results in cleanup rewriting the tar file (all over again). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)