unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Peter P." <peterparker@fastmail.com>
To: David Bremner <david@tethera.net>,
	notmuch@notmuchmail.org, xapian-discuss@lists.xapian.org
Subject: Re: Internal error: Message without type term
Date: Tue, 4 Jul 2023 22:37:11 +0200	[thread overview]
Message-ID: <20230704203711.ccyuczsacohinswr@fastmail.com> (raw)
In-Reply-To: <20230704002007.GS26907@survex.com>

Olly, David, list(s),

* Olly Betts <olly@survex.com> [2023-07-04 02:20]:
[...]
> Was this database originally created by Xapian < 1.4.22?  It looks
> like it could be the result of the bug fixed in 1.4.22 with handling
> commit() failure on disk full.
Indeed I have Debian's libxapian30 package installed which reports
version 1.4.22-1 and I *might* have ran out of disk space in the not too
distant past.

> > >> 2)  Move the database out of the way, re-run notmuch new,
> > >> and restore your state using "notmuch restore < notmuch-db.txt"
> > >  
> > > I'd be fine regenerating the entire database without a backup dump even,
> > > I don't think there is anything in there that can't be regernerated,
> > > no?
> > 
> > The main thing that would be lost is tags that are not synched to
> > maildir flags. In the "standard" workflow "inbox" is such a tag.
> 
> If there's tag data in the database which isn't backed up or synced to
> maildir flags, you may be able to rescue it using:
> 
> https://git.xapian.org/?p=xapian;a=blob;f=README.notmuch;hb=refs/heads/notmuch-tag-rescue-hack
> 
> This creates a file with the tag data in the format `notmuch restore`
> expects.  I'd expect this would work for your database as the termlist
> table is mostly OK.
Thank you, I did meanwhile recreate the database from scratch and it
seems to work™.

best, Peter\r

      reply	other threads:[~2023-07-04 20:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  7:47 Internal error: Message without type term Peter P.
2023-07-03 10:34 ` David Bremner
2023-07-03 10:47   ` Peter P.
2023-07-03 12:26     ` David Bremner
2023-07-03 12:48       ` Peter P.
2023-07-04  0:20       ` Olly Betts
2023-07-04 20:37         ` Peter P. [this message]

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=20230704203711.ccyuczsacohinswr@fastmail.com \
    --to=peterparker@fastmail.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).