Datastore inconsistency

[Roy Teeuwen <ro...@teeuwen.be>]

Hey all,

I had some issues with datastore blob files missing. After running the oak-run datastorecheck I found the path/ids of the blobs that were missing. I fixed it by copying over the blobs from another environment. But alternatively, how could I know which jcr path these blobs actually represent?

Greets,
Roy

Re: Datastore inconsistency

[Wim Symons <wi...@gmail.com>]

Hi Roy,

We did this some time ago. The oak-run datastorecheck has an option for
that: --verbose.

See the list options provided:

Apache Jackrabbit Oak 1.8.9
Option               Description
------               -----------
-?, -h, --help       show help
--consistency        Check consistency
--dump <String>      Dump Path
--id                 Get ids
--ref                Get references
--repoHome <String>  Local repository home folder
--store <String>     Node Store
--track              Force override tracked ids
--verbose            Output backend formatted ids/paths

So run it with --ref --verbose.

I don't know by heart in which version of oak-run this was introduced.

But do note, that the --verbose option introduces a significant difference
in the amount of data which is checked. Without the --verbose, all
generations stored in the JCR are checked, with the --verbose only the
latest generation is checked. (Cfr online compaction -- by default 2
generations are stored in the TarMK).

Kind regards

Wim

On Sun, May 26, 2019 at 2:47 PM Roy Teeuwen <ro...@teeuwen.be> wrote:

> Hey all,
>
> I had some issues with datastore blob files missing. After running the
> oak-run datastorecheck I found the path/ids of the blobs that were missing.
> I fixed it by copying over the blobs from another environment. But
> alternatively, how could I know which jcr path these blobs actually
> represent?
>
> Greets,
> Roy