Matt <mattator at gmail.com> writes:> thanks didn't know about xapian-check ! > the output > ==> docdata: > blocksize=8K items=70 firstunused=3 revision=421 levels=0 root=2 > B-tree checked okay > docdata table structure checked OK > > termlist: > blocksize=8K items=186136 firstunused=62058 revision=421 levels=2 root=12260 > B-tree checked okay > termlist table structure checked OK > > postlist: > blocksize=8K items=2598971 firstunused=61412 revision=421 levels=2 root=49814 > xapian-check: DatabaseCorruptError: Db block overwritten - are there > multiple writers? > ==> suggests there is an error but I couldn't find a fix for it. Should I > just remove the xapian folder and rerun `notmuch new` ?If you have a backup of your tags from notmuch-dump, then yes that's probably a good way forward. I've put the xapian developers in copy in case they are interested in trying to debug this corruption. For those just joining us, this is notmuch 0.29.3 linked against xapian 1.4.15 d
On Tue, Apr 07, 2020 at 05:21:47PM -0300, David Bremner wrote:> Matt <mattator at gmail.com> writes:[...]> > termlist: > > blocksize=8K items=186136 firstunused=62058 revision=421 levels=2 root=12260 > > B-tree checked okay > > termlist table structure checked OK > > > > postlist: > > blocksize=8K items=2598971 firstunused=61412 revision=421 levels=2 root=49814 > > xapian-check: DatabaseCorruptError: Db block overwritten - are there > > multiple writers? > > ==> > suggests there is an error but I couldn't find a fix for it. Should I > > just remove the xapian folder and rerun `notmuch new` ? > > If you have a backup of your tags from notmuch-dump, then yes that's > probably a good way forward.If you don't have a current dump, you may be able to rescue a dump of tags from a broken notmuch database using: https://git.xapian.org/?p=xapian;a=blob;f=README.notmuch;hb=refs/heads/notmuch-tag-rescue-hack That should work if the termlist table is undamaged (as the above appears to show), and may work even if it's damaged.> I've put the xapian developers in copy in > case they are interested in trying to debug this corruption. For those > just joining us, this is notmuch 0.29.3 linked against xapian 1.4.15Was the database created with 1.4.15 too? If it's reproducible, I'm definitely interested. If it isn't reproducible (and/or the data is sensitive) it's much more difficult to usefully investigate. And it may also be due to a non-Xapian issue (a bug in something else or a hardware problem). Cheers, Olly
thanks for the support, since the notmuch database must have been ~7 years long with lots of upgrade, unexpected shutdowns, configuration fiddling I thought it would have been very hard to track down the root cause. If I had had a better idea of the root cause I would have liked to help but all my tags are automatically set so it was simpler to just regenerate the database and that's what I ended up doing. Thanks for the proposition though. Matt 2020?4?8?(?) 0:20 Olly Betts <olly at survex.com>:> > On Tue, Apr 07, 2020 at 05:21:47PM -0300, David Bremner wrote: > > Matt <mattator at gmail.com> writes: > [...] > > > termlist: > > > blocksize=8K items=186136 firstunused=62058 revision=421 levels=2 root=12260 > > > B-tree checked okay > > > termlist table structure checked OK > > > > > > postlist: > > > blocksize=8K items=2598971 firstunused=61412 revision=421 levels=2 root=49814 > > > xapian-check: DatabaseCorruptError: Db block overwritten - are there > > > multiple writers? > > > ==> > > suggests there is an error but I couldn't find a fix for it. Should I > > > just remove the xapian folder and rerun `notmuch new` ? > > > > If you have a backup of your tags from notmuch-dump, then yes that's > > probably a good way forward. > > If you don't have a current dump, you may be able to rescue a dump of > tags from a broken notmuch database using: > > https://git.xapian.org/?p=xapian;a=blob;f=README.notmuch;hb=refs/heads/notmuch-tag-rescue-hack > > That should work if the termlist table is undamaged (as the above > appears to show), and may work even if it's damaged. > > > I've put the xapian developers in copy in > > case they are interested in trying to debug this corruption. For those > > just joining us, this is notmuch 0.29.3 linked against xapian 1.4.15 > > Was the database created with 1.4.15 too? > > If it's reproducible, I'm definitely interested. > > If it isn't reproducible (and/or the data is sensitive) it's much more > difficult to usefully investigate. And it may also be due to a > non-Xapian issue (a bug in something else or a hardware problem). > > Cheers, > Olly