unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Varac <varac@leap.se>, Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Database error
Date: Fri, 20 Apr 2018 09:44:25 -0300	[thread overview]
Message-ID: <87o9ie11zq.fsf@tethera.net> (raw)
In-Reply-To: <152416238134.7508.12807881658685792944@rocinante.bitrigger.de>

Varac <varac@leap.se> writes:

> Hi,
>
> I get a DatabaseError right after initial indexing.
> I can reproduce this with my mails every time.
> First, I remove the whole .notmuch/xapian directory and
> run "notmuch new", which results in a DatabaseError when
> using "xapian-check":
>
>
>   » notmuch new
>   Welcome to a new version of notmuch! Your database will now be upgraded.
>   This process is safe to interrupt.
>   Backing up tags to /home/varac/.offlineimap/Mail/.notmuch/dump-20180419T160138.gz...
>   Your notmuch database has now been upgraded.
>   Processed 148440 total files in 13m 38s (181 files/sec.).
>   Added 140351 new messages to the database.
>
>   » xapian-check .notmuch/xapian 
>   docdata:
>   blocksize=8K items=564 firstunused=7 revision=7 levels=1 root=2
>   B-tree checked okay
>   docdata table structure checked OK
>
>   termlist:
>   blocksize=8K items=305882 firstunused=64506 revision=7 levels=2 root=63491
>   xapian-check: DatabaseError: 1 unused block(s) missing from the free list, first is 0


This is almost certainly a known and recently fixed xapian bug. notmuch
compact is the recommended workaround (or just ignore the message).

>
> After this I try to tun "afew --tag --new -v" but it fails with (I don't know if 
> this is related though):
>
>   Traceback (most recent call last):
>     File "/usr/bin/afew", line 11, in <module>
>       load_entry_point('afew==1.3.0', 'console_scripts', 'afew')()
>     File "/usr/lib/python3/dist-packages/afew/commands.py", line 159, in main
>       inner_main(args, database, query_string)
>     File "/usr/lib/python3/dist-packages/afew/main.py", line 23, in main
>       filter_.run(query_string)
>     File "/usr/lib/python3/dist-packages/afew/filters/BaseFilter.py", line 59, in run
>       for message in self.database.get_messages(query):
>     File "/usr/lib/python3/dist-packages/afew/Database.py", line 93, in get_messages
>       for message in self.do_query(query).search_messages():
>     File "/usr/lib/python3/dist-packages/notmuch/query.py", line 182, in search_messages
>       raise NotmuchError(status)
>   notmuch.errors.XapianError
>

It's hard to say for sure, but it's possible this would be fixed by the
patch

        https://mid.mail-archive.com/20180414014610.15438-4-david@tethera.net

That should be part of a bug-fix release of notmuch fairly soon. You can
also try to find a subset of mail reproducing the problem. I don't
know what that afew invokation is trying to do. Can you reproduce the
problem using the notmuch CLI?

d

  reply	other threads:[~2018-04-20 12:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 18:26 Database error Varac
2018-04-20 12:44 ` David Bremner [this message]
2018-04-20 12:57   ` Varac
  -- strict thread matches above, loose matches on Subject: below --
2016-08-14 17:14 database error Ken
2016-08-14 23:27 ` David Bremner
2016-08-15  7:37   ` Tomi Ollila

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=87o9ie11zq.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    --cc=varac@leap.se \
    /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).