1 Return-Path: <amdragon@gmail.com>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 7BC7B431FB6
\r
6 for <notmuch@notmuchmail.org>; Fri, 28 Jan 2011 08:35:07 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001,
\r
13 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id YQ8KLddUJvuA for <notmuch@notmuchmail.org>;
\r
17 Fri, 28 Jan 2011 08:35:06 -0800 (PST)
\r
18 Received: from mail-vw0-f53.google.com (mail-vw0-f53.google.com
\r
19 [209.85.212.53]) (using TLSv1 with cipher RC4-MD5 (128/128 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id 7929A431FB5
\r
22 for <notmuch@notmuchmail.org>; Fri, 28 Jan 2011 08:35:06 -0800 (PST)
\r
23 Received: by vws8 with SMTP id 8so1299179vws.26
\r
24 for <notmuch@notmuchmail.org>; Fri, 28 Jan 2011 08:35:03 -0800 (PST)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
\r
26 h=domainkey-signature:mime-version:sender:in-reply-to:references:date
\r
27 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
\r
28 bh=3XBKkErOTfs11dGXuzaBWWgyfgh3B+fBA/kHEbj+bJU=;
\r
29 b=sm9twBYvjoTfULT4bfdYLEEaKdoAqkfmmQ7Zs5n2nEoqlcdSNDYE7tsWATUExdS4EW
\r
30 m0Z/UpPYs4AwL3sQ6mGPsI1JgQALl52P2J8ZOsZY5xWT2Aqub6nLLWAcZq6f22/Fm9Yo
\r
31 jGKFORst4hKE1ygO/u2KhlHOtnVLHOis5AXPU=
\r
32 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
\r
33 h=mime-version:sender:in-reply-to:references:date
\r
34 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
\r
35 b=bQ1LeVrHyBP4SVoS8fT3GPxjkbVOSU8KW80prwaKc/9bJ2Uhf9a8phKVyA2dcWrTsH
\r
36 VWVS1JbiiXINF8sHs9ND+UluH3juKciuTyW0u57db/eZD5apyRPFD2gxctQE1VbQ51gI
\r
37 e7ljifzLe0VG9aXmnIfZ9M7G8Wjir+N1q+HEY=
\r
39 Received: by 10.229.90.200 with SMTP id j8mr371587qcm.268.1296232503187; Fri,
\r
40 28 Jan 2011 08:35:03 -0800 (PST)
\r
41 Sender: amdragon@gmail.com
\r
42 Received: by 10.229.97.143 with HTTP; Fri, 28 Jan 2011 08:35:03 -0800 (PST)
\r
43 In-Reply-To: <87d3nhe3g9.fsf@steelpick.2x.cz>
\r
44 References: <87d3nhe3g9.fsf@steelpick.2x.cz>
\r
45 Date: Fri, 28 Jan 2011 11:35:03 -0500
\r
46 X-Google-Sender-Auth: OvtkSP21LeXb3LPBBwXljMNq7vs
\r
47 Message-ID: <AANLkTinW_n+zMtLC-fy=naUGsAiFDwdd-mAqSWEDvF=W@mail.gmail.com>
\r
48 Subject: Re: Xapian locking errors with custom query parser
\r
49 From: Austin Clements <amdragon@mit.edu>
\r
50 To: Michal Sojka <sojkam1@fel.cvut.cz>
\r
51 Content-Type: multipart/alternative; boundary=001636aa2b74e61969049aeaa589
\r
52 Cc: notmuch@notmuchmail.org
\r
53 X-BeenThere: notmuch@notmuchmail.org
\r
54 X-Mailman-Version: 2.1.13
\r
56 List-Id: "Use and development of the notmuch mail system."
\r
57 <notmuch.notmuchmail.org>
\r
58 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
59 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
60 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
61 List-Post: <mailto:notmuch@notmuchmail.org>
\r
62 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
63 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
64 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
65 X-List-Received-Date: Fri, 28 Jan 2011 16:35:07 -0000
\r
67 --001636aa2b74e61969049aeaa589
\r
68 Content-Type: text/plain; charset=ISO-8859-1
\r
70 This should most definitely not happen. I'll look in to it.
\r
72 On Fri, Jan 28, 2011 at 5:18 AM, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
\r
76 > when I switched to using your custom query parser I started experiencing
\r
77 > "Unable to get write lock" errors when I run my initial tagging script.
\r
78 > I thought that this was because I run the script while processing the
\r
79 > mail in Emacs, but today I realized that this happens even without Emacs
\r
80 > and that it can be reproduced by a simple command below.
\r
82 > i=0; while notmuch tag +xxx tag:whatever; do i=$((i+1)); echo $i; done
\r
84 > It seems that sometimes the unlocking of the Xapian database happens
\r
85 > somewhat lazily and when the subsequent command starts I get:
\r
87 > A Xapian exception occurred opening database: Unable to get write lock on
\r
88 > /home/wsh/mail/.notmuch/xapian: already locked
\r
90 > This happens almost regularly after a few iterations of the loop even if
\r
91 > the query doesn't match anything.
\r
93 > Do you have an idea what may cause this?
\r
95 > Can you reproduce this on your system?
\r
97 > The version I use can be obtained from
\r
99 > git://rtime.felk.cvut.cz/notmuch.git custom-query-pasrser
\r
103 > _______________________________________________
\r
104 > notmuch mailing list
\r
105 > notmuch@notmuchmail.org
\r
106 > http://notmuchmail.org/mailman/listinfo/notmuch
\r
109 --001636aa2b74e61969049aeaa589
\r
110 Content-Type: text/html; charset=ISO-8859-1
\r
111 Content-Transfer-Encoding: quoted-printable
\r
113 This should most definitely not happen. =A0I'll look in to it.<br><br><=
\r
114 div class=3D"gmail_quote">On Fri, Jan 28, 2011 at 5:18 AM, Michal Sojka <sp=
\r
115 an dir=3D"ltr"><<a href=3D"mailto:sojkam1@fel.cvut.cz">sojkam1@fel.cvut.=
\r
116 cz</a>></span> wrote:<br>
\r
117 <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
\r
118 x #ccc solid;padding-left:1ex;">Hi Austin,<br>
\r
120 when I switched to using your custom query parser I started experiencing<br=
\r
122 "Unable to get write lock" errors when I run my initial tagging s=
\r
124 I thought that this was because I run the script while processing the<br>
\r
125 mail in Emacs, but today I realized that this happens even without Emacs<br=
\r
127 and that it can be reproduced by a simple command below.<br>
\r
129 i=3D0; while notmuch tag +xxx tag:whatever; do i=3D$((i+1)); echo $i; done<=
\r
132 It seems that sometimes the unlocking of the Xapian database happens<br>
\r
133 somewhat lazily and when the subsequent command starts I get:<br>
\r
135 A Xapian exception occurred opening database: Unable to get write lock on /=
\r
136 home/wsh/mail/.notmuch/xapian: already locked<br>
\r
138 This happens almost regularly after a few iterations of the loop even if<br=
\r
140 the query doesn't match anything.<br>
\r
142 Do you have an idea what may cause this?<br>
\r
144 Can you reproduce this on your system?<br>
\r
146 The version I use can be obtained from<br>
\r
148 =A0git://<a href=3D"http://rtime.felk.cvut.cz/notmuch.git" target=3D"_blan=
\r
149 k">rtime.felk.cvut.cz/notmuch.git</a> custom-query-pasrser<br>
\r
153 _______________________________________________<br>
\r
154 notmuch mailing list<br>
\r
155 <a href=3D"mailto:notmuch@notmuchmail.org">notmuch@notmuchmail.org</a><br>
\r
156 <a href=3D"http://notmuchmail.org/mailman/listinfo/notmuch" target=3D"_blan=
\r
157 k">http://notmuchmail.org/mailman/listinfo/notmuch</a><br>
\r
158 </blockquote></div><br>
\r
160 --001636aa2b74e61969049aeaa589--
\r