From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=-3.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id A5D9F1F47C for ; Fri, 30 Aug 2024 21:12:04 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=baylibre-com.20230601.gappssmtp.com header.i=@baylibre-com.20230601.gappssmtp.com header.a=rsa-sha256 header.s=20230601 header.b=ROGkMLKz; dkim-atps=neutral Received: by mail-pj1-x1033.google.com with SMTP id 98e67ed59e1d1-2d3b5f2f621so1702316a91.1 for ; Fri, 30 Aug 2024 14:12:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20230601.gappssmtp.com; s=20230601; t=1725052319; x=1725657119; darn=public-inbox.org; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:from:to:cc:subject:date:message-id :reply-to; bh=iwCmN9uXMRe+86sM/tUzBGqKFbd1Ai6XsGi5bMcjvLs=; b=ROGkMLKz4v5l1EZdyvw4RJvaO27GdrlRbYL1EnBF759Uq2iS7j84j0vp683e9S9qdP OD8PrFK642o3ARrFI+xvtLQBuyzSmbOEhfx3yHgHidLyvyQS9Z5WcYR6Kvr7nD5AnY8p pW96pM6yqgiXjyT9VuoyAIsUa/Vki221wltKfHN7PVnn94A117lg/05VaheWtudwG3YC or9OD97+UpercJKi/9DYJEL7zgzRmXEifts6eQOxtsbSd7aKgrKk9Yy//ENy/mDVs10X iS6NYAr21996eFqBSqTJ5H7e8UrbOYsOoPMzFejcN8TXHmYp12TDbQv+wYE+MMWhzOJ+ VWAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725052319; x=1725657119; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=iwCmN9uXMRe+86sM/tUzBGqKFbd1Ai6XsGi5bMcjvLs=; b=tmedMyo+jXhbB5t3YRqhytK6Gm1lb/4GcnmcIoP+YHlmPQxdzGSc5eym5GymVxl/hc zyqZh637qJhTR5b5P3FaWIBNzC9GHkeCl/Vj6wbtkgt8BFpJg/PaUOf5OX3K3KoytE+l bOO3z0dRpvSv8pByTdW5n8SKxt2fXlxsRAtio9lnhUYQVu/qmUrUfXfgCx5/7N/pMW5U FIl61LXgB+EAKIcqBUp0RhLOtlc8Ssfq+zSPQyFUCS/aMkhyvHJGX3G3ON/1M2za+lo1 IySIMuYPbteni6mEzsuRQbU5Du4PMe02JaI9vUfnGn0mNlKpH/uYcbswea951wrtevMW +AFQ== X-Gm-Message-State: AOJu0YzOHSJFI522x45euCk90TuTZx3ml0cuR8+9IuB/TkvkgnfLPUWy KPmCvt75Mf9PoHrRq3VBX+GZWLnHh9Rls1K6+Vm95wQTh8kj57IUXeqQ0LQIuHk= X-Google-Smtp-Source: AGHT+IEAy7Tigzi0b8N2C3VmigmTki0rnAOEMQrgqeRAsnJeR87W6lfyaOADqpxe1EV6pGZbp5bKtA== X-Received: by 2002:a17:90a:ce8f:b0:2d1:ca16:554d with SMTP id 98e67ed59e1d1-2d893284d70mr340662a91.4.1725052319292; Fri, 30 Aug 2024 14:11:59 -0700 (PDT) Received: from localhost ([71.212.170.185]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2d85b0fdf2csm4354501a91.2.2024.08.30.14.11.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 30 Aug 2024 14:11:58 -0700 (PDT) From: Kevin Hilman To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Exception: Expected block 59423 to be level 2, not 0 In-Reply-To: <20240830204329.M646998@dcvr> References: <20240830204329.M646998@dcvr> Date: Fri, 30 Aug 2024 14:11:58 -0700 Message-ID: <7hmsktbtr5.fsf@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Eric Wong writes: > Kevin Hilman wrote: >> On Fri, Aug 30, 2024 at 12:40=E2=80=AFPM Kevin Hilman 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. >>=20 >> 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). 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. > Any failing HW (SMART errors, dmesg), dirty shutdowns, or non-ECC RAM? Not that I know of. > Otherwise it might be something the xapian-discuss list can help with... OK, thanks for the pointer. Kevin [1] $ xapian-check 2 F Database couldn't be opened for reading: DatabaseCorruptError: Expected blo= ck 59423 to be level 2, not 0 Continuing check anyway docdata: B-tree checked okay docdata table structure checked OK termlist: xapian-check: DatabaseCorruptError: Block overwritten - run xapian-check on= this database