unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Kevin Hilman <khilman@baylibre.com>
Cc: meta@public-inbox.org
Subject: Re: Exception: Expected block 59423 to be level 2, not 0
Date: Fri, 30 Aug 2024 21:40:17 +0000	[thread overview]
Message-ID: <20240830214018.M16439@dcvr> (raw)
In-Reply-To: <7hmsktbtr5.fsf@baylibre.com>

Kevin Hilman <khilman@baylibre.com> wrote:
> Indeed, xapian-check found a corrupt database in
> ~/.local/share/lei/store/ei15/2, but and spits out the same error as
> $SUBJECT.  However, it is not able to correct it[1]  :(
> 
> Assuming my xapian db is unrecoverable, is there any way to rebuild it?
> or do I just need to delete it & re-run all my saved searches,
> presumably losing all the past mail from any searches.

I haven't tried it, but probably removing the Xapian directories
and `lei reindex' with current public-inbox.git

I just pushed out some changes the other week which should make
it more robust against missing Xapian docs, but have yet to test
against non-existent Xapian.

> > Any failing HW (SMART errors, dmesg), dirty shutdowns, or non-ECC RAM?
> 
> Not that I know of.

I do wonder what caused it, AFAIK there's nothing in our Xapian
library usage which might cause this.  Perhaps an FS-level fsck
would be helpful.  Similarly, I would do git fsck and/or gc
and try the integrity_check pragma in SQLite just in case...

      reply	other threads:[~2024-08-30 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30 19:40 Exception: Expected block 59423 to be level 2, not 0 Kevin Hilman
2024-08-30 19:44 ` Kevin Hilman
2024-08-30 20:43   ` Eric Wong
2024-08-30 21:11     ` Kevin Hilman
2024-08-30 21:40       ` Eric Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240830214018.M16439@dcvr \
    --to=e@80x24.org \
    --cc=khilman@baylibre.com \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).