From: Olly Betts <olly@survex.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Xapian Discussion <xapian-discuss@lists.xapian.org>,
"notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: How to recover from this permanent fatal error?
Date: Sun, 6 Jun 2021 11:08:51 +0100 [thread overview]
Message-ID: <20210606100851.GA18586@survex.com> (raw)
In-Reply-To: <CAMP44s0rGUsvD3LhFB199Y52WNATda7MfmKha_OHAPrfDWiPtw@mail.gmail.com>
On Sat, Jun 05, 2021 at 11:40:58PM -0500, Felipe Contreras wrote:
> % xapian-core/bin/xapian-check ~/mail/.notmuch/xapian/termlist.glass
> termlist:
> xapian-core/bin/.libs/lt-xapian-check: DatabaseCorruptError: Db block
> overwritten - are there multiple writers?
Ah - this tool currently requires the termlist table to be undamaged
enough to at least scan through.
You could try commenting out the body of GlassTable::set_overwritten()
in xapian-core/backends/glass/glass_table.cc so it keeps going instead
of throwing this exception, which might allow it to usefully recover
some or all tags. If you (or anyone) try that and it works let me know
and I can patch the branch to emit a warning message and continue there.
If the postlist table is readable it'd be possible to rescue the tag
data from there instead, but that's more complicated to do because
the tags would need collating for each message.
Cheers,
Olly
next prev parent reply other threads:[~2021-06-06 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 0:44 How to recover from this permanent fatal error? Felipe Contreras
2021-06-05 1:37 ` David Bremner
2021-06-05 1:40 ` Felipe Contreras
2021-06-05 2:43 ` Olly Betts
2021-06-05 14:39 ` Felipe Contreras
2021-06-06 1:45 ` Olly Betts
2021-06-06 4:40 ` Felipe Contreras
2021-06-06 10:08 ` Olly Betts [this message]
2021-06-06 12:48 ` Felipe Contreras
2021-06-07 3:45 ` Olly Betts
2021-06-07 7:07 ` Felipe Contreras
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210606100851.GA18586@survex.com \
--to=olly@survex.com \
--cc=felipe.contreras@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=xapian-discuss@lists.xapian.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).