From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.2 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,
	T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no
	version=3.4.6
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 2836C1F47A;
	Fri, 30 Aug 2024 21:40:18 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=80x24.org;
	s=selector1; t=1725054018;
	bh=MFfHX4031jNn8B+H/+OaowfrDzzX5DOCCZylmTHTRvY=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=yUzsjXhzzPphRCdEL+4Ql/eWJyFtCwmrZB4CtpEYrfn987NUwH7uwh+yqrO2yxAU8
	 /ex7TmuR/3xGqtbUVnqNv2VVzIYqtFFi9iSC/pjgXqN7Ht+RpnG4H2VUnOlLKLOae8
	 vW73Y+cc+c6/y2qrE2cSDPfV25z4laBy92KQuWXU=
Date: Fri, 30 Aug 2024 21:40:17 +0000
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
Message-ID: <20240830214018.M16439@dcvr>
References: <CAOi56cWNQOPmvEFRNsafRzKYdpgSbqZLUDZH57yynZxCjdtUiw@mail.gmail.com>
 <CAOi56cWQEZM31JFe2mAXMQWbmLetLZ=LeiVqZzRC97DOFF33Aw@mail.gmail.com>
 <20240830204329.M646998@dcvr>
 <7hmsktbtr5.fsf@baylibre.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <7hmsktbtr5.fsf@baylibre.com>
List-Id: <meta.public-inbox.org>

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...