unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Patrick Totzke <patricktotzke@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch python bindings corrupt db index (was: gmail importer script)
Date: Tue, 11 Dec 2012 18:26:38 +0000	[thread overview]
Message-ID: <20121211182638.27237.98903@brick.lan> (raw)
In-Reply-To: <CAHmME9phAD0JKHDf+1KuCPyo4WXpDW5NESAE_iT3Ruv3bEVCuw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]

Quoting Jason A. Donenfeld (2012-12-11 13:47:32)
> On Tue, Dec 11, 2012 at 11:04 AM, Patrick Totzke
> <patricktotzke@gmail.com> wrote:
> > I ended up killing the process after i saw that ETA was >3h.
> 
> Gmail's bottleneck. Very unfortunate. Leave it going over night.

OK, i assumed i'd not have to download all messages because i already have them
on disk -- synced via offlineimap. but then i remembered that OI stores uses
its own naming scheme for the files in a maildir. so thats probably why your script
did not realize theyre already there. (maybe it should? it could look up the MIDs from notmuch)

> > This broke my index!
> >
> > afterwards, a `notmuch new` printed
> >
> > A Xapian exception occurred creating a directory: Expected block
> > 485 to be level 1, not 0.
> >
> > I wasnt able to properly read the index anymore and had to
> > restore an old index dump. not cool!
> 
> 
> Can you provide any more information about this? The script properly
> uses atomic transactions. Any corruption here is the result of a
> notmuch library bug, which should be investigated.

i am kind of reluctant to reproduce this again (on my work-desktop).
All i did was start your script, writing to the index in another terminal in between (using alot)
possibly my cronjob fired a "notmuch new; afew.." in between also.
when I killed your script the index war broken.

Can i turn on some global logging for notmuch to debug this?
Maybe libnotmuch had trouble with so many db-writes at a time?

/p



[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAlDHet4ACgkQlDQDZ9fWxap4BgCdFxBrgs+jIadzi/xvsAVB9mnY
s2UAoJZXSab5ftLEa1+d7ORHFiHsJy62
=WT0i
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-12-11 18:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 13:47 notmuch python bindings corrupt db index (was: gmail importer script) Jason A. Donenfeld
2012-12-11 18:26 ` Patrick Totzke [this message]
2012-12-12 18:35   ` Jason A. Donenfeld
2012-12-12 20:49     ` Austin Clements
2012-12-12 21:26       ` David Bremner
2012-12-13 14:33         ` Jason A. Donenfeld
2012-12-13 14:32       ` Jason A. Donenfeld
2012-12-13 16:16         ` Patrick Totzke
2012-12-15  6:18         ` Austin Clements
2012-12-15  8:25           ` Jason A. Donenfeld

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=20121211182638.27237.98903@brick.lan \
    --to=patricktotzke@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=notmuch@notmuchmail.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).