It turns out that the IO error was real. I've manage to "fix" that problem.
I'm still left with corrupted data though:
2019/04/16 15:18:14 sync: /bs/ -> /sto-s3/: error copying
sha224-3c233f61cf607adf2671b9494a87647ef83417f098b8f195d415e536: Read data
has unexpected digest
1b53683417460c294ebfe2bd13028444291edb536193055925225daf
I tried recovery and reindexing, perkeepd -recovery=2 -reindex=true, which
after a long while ends in
2019/04/16 15:03:43 Reindexing at
sha224-ffe519c7b4d5092c677cc782889dea138ae0c6946c506e0e518a50d9
2019/04/16 15:03:43 index: error parsing tag: taglib: format not recognised
(not ID3)
2019/04/16 15:03:43 Caught panic installer handlers: Error reindexing
/index/: 1 blobs failed to re-index
goroutine 1 [running]:
runtime/debug.Stack(0xc4200c8190, 0x2, 0xc42710f680)
/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-go-1.10.8/share/go/src/runtime/debug/stack.go:24
+0xa7
<snip>
main.main()
/build/go/src/perkeep.org/server/perkeepd/camlistored.go:906 +0x29
Error parsing config: Caught panic: Error reindexing /index/: 1 blobs
failed to re-index
This seems related to https://github.com/perkeep/perkeep/issues/1122
Loosing the data from my most recent pk-put is not a problem for me, but
what I'd love to know is this: *Is there a way to return my blob store and
index to a sane state so that I can go on using perkeep?*
Cheers,
Anders
--
You received this message because you are subscribed to the Google Groups
"Perkeep" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
