On 2025-02-04 17:18:33, Andrej Alberstejn wrote:
> On Tue, Feb 4, 2025 at 4:23 PM David Bremner <david@tethera.net> wrote:
> >
> > Andrey Albershteyn <aalbersh@redhat.com> writes:
> >
> >
> > > Any guesses what could be the reason? The failure of 'notmuch new'
> > > suggests to me that it's not just corrupted database.
> > >
> >
> > Hmm. Why not? At least initially it looks like a corrupted database to
> > me.
> >
> > > Is there way to check and repair the database by the way?
> > >
> >
> > You can at least check it with xapian-check; it can apparently only
> > repair the older chert format
> 
> hmm, doesn't seem to do anything. Using F flag to repair also shows this error
> 
> $ xapian-check ~/.mail/gmail/inbox/.notmuch/xapian"
> docdata:
> blocksize=8K items=2 firstunused=3 revision=6741471 levels=0 root=2
> B-tree checked okay
> docdata table structure checked OK
> 
> termlist:
> blocksize=8K items=310042 firstunused=74053 revision=6741471 levels=2 root=72342
> xapian-check: DatabaseCorruptError: Block overwritten - run
> xapian-check on this database
> 
> Any other thoughts?

I ended up removing database, and running 'notmuch new' to re-index
everything. This is problematic as now all my emails are marked as
unread, but I figured this out by marking all older mails as read.

Didn't found the reason for database corruption.

-- 
- Andrey

_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org