unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Mike Hommey <mh@glandium.org>
To: notmuch@notmuchmail.org
Subject: Error while compacting: Bad position key
Date: Tue, 10 Jul 2018 12:16:28 +0900	[thread overview]
Message-ID: <20180710031628.kowwcvfg6bmx4iyv@glandium.org> (raw)

Hi,

When running `notmuch compact` today, it stopped with the following
output:

Compacting database...
compacting table postlist
     Reduced by 25% 648656K (2498904K -> 1850248K)
compacting table docdata
     Reduced by 15% 24K (152K -> 128K)
compacting table termlist
     Reduced by 1% 27008K (2211800K -> 2184792K)
compacting table position
Error while compacting: Bad position key

Compaction failed: A Xapian exception occurred

Running xapian-check says:

docdata:
blocksize=8K items=2677 firstunused=19 revision=15425 levels=1 root=17
B-tree checked okay
docdata table structure checked OK

termlist:
blocksize=8K items=2986940 firstunused=276475 revision=15425 levels=2 root=271786
B-tree checked okay
doclen not within bounds
(...)
doclen not within bounds
termlist table errors found: 107982

postlist:
blocksize=8K items=16090818 firstunused=312363 revision=15425 levels=3 root=249894
B-tree checked okay
postlist table structure checked OK

position:
blocksize=8K items=236476398 firstunused=653990 revision=15425 levels=3 root=598684
xapian-check: DatabaseError: Block 459158 item 179: not in sorted order


Is there something I can do, or do I essentially need to completely
rebuild the database (and if so, what's the best way to do it?)

Cheers,

Mike

             reply	other threads:[~2018-07-10  3:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10  3:16 Mike Hommey [this message]
2018-07-12 11:22 ` Error while compacting: Bad position key David Bremner
2018-07-13 20:06   ` Olly Betts

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=20180710031628.kowwcvfg6bmx4iyv@glandium.org \
    --to=mh@glandium.org \
    --cc=notmuch@notmuchmail.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).