Gregor Zattler writes:
> Hi David, Olly, notmuch and xapian developers,
> * David Bremner [11. Feb. 2021]:
>> David Bremner writes:
>> As a kind of desperation move, you could try bisecting your mailstore,
>> to see how small of a set of messages you can duplicate the problem
>> with.
>
> this
Hi David, Olly, notmuch and xapian developers,
* David Bremner [11. Feb. 2021]:
> David Bremner writes:
> As a kind of desperation move, you could try bisecting your mailstore,
> to see how small of a set of messages you can duplicate the problem
> with.
this I did, somehow. I found the
Hi Olly, David, xapian and notmuch developers,
* Olly Betts [12. Feb. 2021]:
> On Thu, Feb 11, 2021 at 06:53:27AM -0400, David Bremner wrote:
>> At this point I don't really have any good ideas, so I'm waiting for
>> results from the 1.4.18 trial.
>
> I've uploaded a backport, but it's the first
Hi Olly, notmuch and xapian developers,
sorry for late answer, I had problems with the test system:
* Olly Betts [09. Feb. 2021]:
> On Wed, Feb 03, 2021 at 07:59:43AM -0400, David Bremner wrote:
>> Gregor Zattler writes:
>>> A Xapian exception occurred finding message: Db block overwritten -
On Thu, Feb 11, 2021 at 06:53:27AM -0400, David Bremner wrote:
> At this point I don't really have any good ideas, so I'm waiting for
> results from the 1.4.18 trial.
I've uploaded a backport, but it's the first backport of xapian-core to
buster so it'll need manual approval. Hopefully that'll
Gregor Zattler writes:
> Hi David, notmuch and xapian developers,
> * David Bremner [03. Feb. 2021]:
>
>
>> Olly Betts mentioned in a different thread that he will build a version
>> of xapian 1.4.18 for buster backports, so trying with that is probably a
>> good step when it is available.
>
>
On Wed, Feb 03, 2021 at 07:59:43AM -0400, David Bremner wrote:
> Gregor Zattler writes:
> > A Xapian exception occurred finding message: Db block overwritten - are
> > there multiple writers?.
>
> I have included the Xapian list in copy in case that message rings a
> bell.
There was a bug
Hi David, notmuch and xapian developers,
* David Bremner [03. Feb. 2021]:
> Gregor Zattler writes:
>>
>> Installed notmuch-dbgsym (0.28.4-1) and gdb.
>>
>> grfz@mic:/etc$ gdb --args notmuch new
>> [...]
>> (gdb) b notmuch-new.c:420
>> Breakpoint 1 at 0x10601: file notmuch-new.c, line 421.
>>
Gregor Zattler writes:
>
> Installed notmuch-dbgsym (0.28.4-1) and gdb.
>
> grfz@mic:/etc$ gdb --args notmuch new
> [...]
> (gdb) b notmuch-new.c:420
> Breakpoint 1 at 0x10601: file notmuch-new.c, line 421.
> (gdb) run
> Starting program: /usr/bin/notmuch new
> [Thread debugging using
Gregor Zattler writes:
>
> 0 (master *) grfz@no:~/Mail/.notmuch$ stat --format "%Y" ~/Mail/inbox/cur
> 1612091679
> 0 (master *) grfz@no:~/Mail/.notmuch$ stat --format "%y" ~/Mail/inbox/cur
> 2021-01-31 12:14:39.771049424 +0100
> 0 (master *) grfz@no:~/Mail/.notmuch$
> 0 (master *)
Hi David, notmuch developers,
* Gregor Zattler [31. Jan. 2021]:
> I'll redo idea #2 on my laptop and will report it's results.
Now on the laptop:
grfz@no:~/Mail/.notmuch$ nice ionice -c 3 notmuch new
Welcome to a new version of notmuch! Your database will now be upgraded.
This process is safe
Hi David, notmuch developers,
thanks a lot: your second idea this time showed a database
corruption instead of an OOM.
The first idea showed, that there is data missing in the
database:
* David Bremner [30. Jan. 2021]:
Since idea #1 involves removing the xapian database I first
tried idea #2:
Gregor Zattler writes:
> Hi notmuch developers,,
> * Gregor Zattler [14. Dez. 2020]:
>> notmuch new still corrupts the database, the second notmuch new
>> invocation finds emails the first did not find.
>
> I'm still searching for the reason notmuch chokes on my mails.
>
> I assembled a HP
Hi notmuch developers,,
* Gregor Zattler [14. Dez. 2020]:
> notmuch new still corrupts the database, the second notmuch new
> invocation finds emails the first did not find.
I'm still searching for the reason notmuch chokes on my mails.
I assembled a HP MicroServer, installed basic debian
14 matches
Mail list logo