A corrupt index
Adam Sjøgren
asjo at koldfront.dk
Mon Nov 15 20:45:15 GMT 2021
Hi,
We have an index which is around 1.1 TB on disk, which has started
giving an error when I try to replace or delete a single, specific
document:
[M] DELETE DOCUMENT FROM INDEX 10491876
Operation "eq": no method found,
left argument in overloaded package Search::Xapian::DatabaseError,
right argument has no overloaded magic at /usr/share/perl5/MCE/Signal.pm line 306, <__ANONIO__> line 1290.
Running xapian-check gives:
$ xapian-check ./index
record:
baseA blocksize=8K items=10442915 lastblock=221214 revision=5434326 levels=3 root=1332
B-tree checked okay
record table structure checked OK
termlist:
baseA blocksize=8K items=20885830 lastblock=10207839 revision=5434326 levels=3 root=7090
Failed to check B-tree: DatabaseError: Key >= right dividing key in level above
postlist:
baseA blocksize=8K items=827807972 lastblock=17007553 revision=5434326 levels=4 root=755
B-tree checked okay
postlist table structure checked OK
position:
baseA blocksize=8K items=13525517523 lastblock=118173891 revision=5434326 levels=4 root=6551
Failed to check B-tree: DatabaseError: Table entry count says 13525517523 but actually counted 13525517278
spelling:
Lazily created, and not yet used.
synonym:
Lazily created, and not yet used.
Total errors found: 2
Is there any chance to fix this without starting over?
If I can just delete some thousands of documents and redo those, it
would be much better for me than having to recreate the entire index.
(We have had some problems recently with the introduction of a new kind
of error, making the indexing program crash in "interesting" ways, so I
am not in doubt that this is a "self-inflicted wound").
I think the index is chert (there is an 'iamchert' file), it's on an
Ubuntu 18.04 server with libxapian30 1.4.5-1ubuntu0.1.
Best regards,
Adam
--
"It's the Disneyland-law Adam Sjøgren
So far out it makes anarchy a bore" asjo at koldfront.dk
More information about the Xapian-discuss
mailing list