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 20:43:29 +0000	[thread overview]
Message-ID: <20240830204329.M646998@dcvr> (raw)
In-Reply-To: <CAOi56cWQEZM31JFe2mAXMQWbmLetLZ=LeiVqZzRC97DOFF33Aw@mail.gmail.com>

Kevin Hilman <khilman@baylibre.com> wrote:
> On Fri, Aug 30, 2024 at 12:40 PM Kevin Hilman <khilman@baylibre.com> wrote:
> >
> > I recently started seeing this error for `lei up`:
> >
> >   $ lei up -v dummy
> >   Exception: Expected block 59423 to be level 2, not 0
> >
> > The same thing happens when trying an edit-search:
> >
> >   $ lei edit-search dummy
> >   Exception: Expected block 59423 to be level 2, not 0
> >
> > The same thing happens whether "dummy" is a valid saved-search or not.
> > A bit of searching suggests that this is a xapian error.  I have
> > xapian-tools installed on this server, should I run some checks on the
> > xapian db?  If so, where is it stored?  Everything I find under
> > ~/.local/share/lei seems to be sqlite3 db.
> 
> I forgot to mention, I'm running the v1.9.0 tag of public-inbox, but
> also tried with the master branch and got the same results.

This looks like file corruption of some sort with Xapian...
Not my area of expertise.

Perhaps xapian-check(1) on each of the 0..$N directories under
~/.local/share/lei/store/ei15 would help (where $N is 3 on most
SMP systems, YMMV).

Any failing HW (SMART errors, dmesg), dirty shutdowns, or non-ECC RAM?
Otherwise it might be something the xapian-discuss list can help with...

  reply	other threads:[~2024-08-30 20:43 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 [this message]
2024-08-30 21:11     ` Kevin Hilman
2024-08-30 21:40       ` Eric Wong

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=20240830204329.M646998@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).