Re: How to recover from this permanent fatal error?

Olly Betts wrote: > On Sun, Jun 06, 2021 at 07:48:39AM -0500, Felipe Contreras wrote: > > On Sun, Jun 6, 2021 at 5:08 AM Olly Betts 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

Re: How to recover from this permanent fatal error?

On Sun, Jun 06, 2021 at 07:48:39AM -0500, Felipe Contreras wrote: > On Sun, Jun 6, 2021 at 5:08 AM Olly Betts 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

Re: How to recover from this permanent fatal error?

On Sun, Jun 6, 2021 at 5:08 AM Olly Betts 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

Re: How to recover from this permanent fatal error?

On Sat, Jun 05, 2021 at 11:40:58PM -0500, Felipe Contreras wrote: > % xapian-core/bin/xapian-check ~/mail/.notmuch/xapian/termlist.glass > termlist: > xapian-core/bin/.libs/lt-xapian-check: DatabaseCorruptError: Db block > overwritten - are there multiple writers? Ah - this tool currently

Re: How to recover from this permanent fatal error?

On Sat, Jun 5, 2021 at 8:45 PM Olly Betts wrote: > > On Sat, Jun 05, 2021 at 09:39:28AM -0500, Felipe Contreras wrote: > > On Fri, Jun 4, 2021 at 9:43 PM Olly Betts wrote: > > > I'd suggest trying this simple tool I wrote that can probably rescue the > > > tags from a broken notmuch database

Re: How to recover from this permanent fatal error?

On Sat, Jun 05, 2021 at 09:39:28AM -0500, Felipe Contreras wrote: > On Fri, Jun 4, 2021 at 9:43 PM Olly Betts wrote: > > I'd suggest trying this simple tool I wrote that can probably rescue the > > tags from a broken notmuch database (the tags are the part notmuch can't > > just recreate by

Re: How to recover from this permanent fatal error?

On Fri, Jun 4, 2021 at 9:43 PM Olly Betts wrote: > > On Fri, Jun 04, 2021 at 08:40:56PM -0500, Felipe Contreras wrote: > > On Fri, Jun 4, 2021 at 8:37 PM David Bremner wrote: > > > Felipe Contreras writes: > > > > > > I can't use notmuch anymore, I get this error: > > > > > > > > A Xapian

Re: How to recover from this permanent fatal error?

On Fri, Jun 04, 2021 at 08:40:56PM -0500, Felipe Contreras wrote: > On Fri, Jun 4, 2021 at 8:37 PM David Bremner wrote: > > Felipe Contreras writes: > > > > I can't use notmuch anymore, I get this error: > > > > > > A Xapian exception occurred opening database: The revision being read > > > has

Re: How to recover from this permanent fatal error?

On Fri, Jun 4, 2021 at 8:37 PM David Bremner wrote: > Felipe Contreras writes: > > I can't use notmuch anymore, I get this error: > > > > A Xapian exception occurred opening database: The revision being read > > has been discarded - you should call Xapian::Database::reopen() and > > retry the

Re: How to recover from this permanent fatal error?

Felipe Contreras writes: > Hello, > > I can't use notmuch anymore, I get this error: > > A Xapian exception occurred opening database: The revision being read > has been discarded - you should call Xapian::Database::reopen() and > retry the operation > > Context. In order to investigate a bug

How to recover from this permanent fatal error?

Hello, I can't use notmuch anymore, I get this error: A Xapian exception occurred opening database: The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation Context. In order to investigate a bug about mbsync I moved away the folder