unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Xapian Discussion <xapian-discuss@lists.xapian.org>,
	Felipe Contreras <felipe.contreras@gmail.com>,
	David Bremner <david@tethera.net>,
	"notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: How to recover from this permanent fatal error?
Date: Sun, 6 Jun 2021 07:48:39 -0500	[thread overview]
Message-ID: <CAMP44s3++2o8PLiMy8Lc45RbdyQ5+8zsCzBizK8CtMvo5hG0VQ@mail.gmail.com> (raw)
In-Reply-To: <20210606100851.GA18586@survex.com>

On Sun, Jun 6, 2021 at 5:08 AM Olly Betts <olly@survex.com> wrote:

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

Now I get this:

termlist:
blocksize=8K items=687440 firstunused=152676 revision=2 levels=2 root=749
/home/felipec/contrib/xapian/xapian-core/bin/.libs/lt-xapian-check:
DatabaseError: Block 152676: used more than once in the Btree

-- 
Felipe Contreras

  reply	other threads:[~2021-06-06 12:49 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
2021-06-06 12:48               ` Felipe Contreras [this message]
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=CAMP44s3++2o8PLiMy8Lc45RbdyQ5+8zsCzBizK8CtMvo5hG0VQ@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=david@tethera.net \
    --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).