Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, Austin Clements <amdragon@mit.edu>
From: Patrick Totzke <patricktotzke@gmail.com>
In-Reply-To:
 <CAHmME9q-NbhRC=Be20aW5Vz+swou419zJxZD4O-3PSTJr+K=iQ@mail.gmail.com>
References:
 <CAHmME9phAD0JKHDf+1KuCPyo4WXpDW5NESAE_iT3Ruv3bEVCuw@mail.gmail.com>
	<20121211182638.27237.98903@brick.lan>
	<CAHmME9qafP5He4hYPEAyrtS4hq3CRNKBQfvxvP=r4L6uDeqt1w@mail.gmail.com>
	<20121212204922.GB6187@mit.edu>
	<CAHmME9q-NbhRC=Be20aW5Vz+swou419zJxZD4O-3PSTJr+K=iQ@mail.gmail.com>
Message-ID: <20121213161600.28349.42261@megatron>
User-Agent: alot/0.3.3+
Subject: Re: notmuch python bindings corrupt db index (was: gmail importer
	script)
Date: Thu, 13 Dec 2012 16:16:00 +0000
Cc: notmuch@notmuchmail.org
Precedence: list

Quoting Jason A. Donenfeld (2012-12-13 14:32:53)
> On Wed, Dec 12, 2012 at 9:49 PM, Austin Clements <amdragon@mit.edu> wrote:
> > There should be no way to corrupt the database at this level through
> > the Xapian API, which means nothing libnotmuch can do (much less users
> > of libnotmuch) should be able to corrupt the database.  If you can
> > reproduce the problem, it's probably a serious bug in Xapian, but it
> > could also have been a file system bug or even random file system
> > corruption.
> =

> Well that's... troubling.
> =

> Patrick: could you please backup and try to reproduce? Otherwise I'll
> assume this was a one-off situation.


I tried it again, concurrently triggered some modifications
and killed the process afer a while.
(my modifications were not flushed during the run of your script as
the index was locked)
The index seems to be OK. So I'm afraid I cannot reproduce this reliably.
/p