From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id IIbbOYgVImARLwAA0tVLHw (envelope-from ) for ; Tue, 09 Feb 2021 04:54:32 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id KMYJNYgVImDmdQAAbx9fmQ (envelope-from ) for ; Tue, 09 Feb 2021 04:54:32 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [144.217.243.247]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (2048 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 0FA9E9400EA for ; Tue, 9 Feb 2021 04:54:31 +0000 (UTC) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 74C0C1FBFA; Mon, 8 Feb 2021 23:54:19 -0500 (EST) X-Greylist: delayed 1193 seconds by postgrey-1.36 at nmbug; Mon, 08 Feb 2021 23:54:17 EST Received: from thyestes.tartarus.org (thyestes.tartarus.org [5.196.91.86]) by mail.notmuchmail.org (Postfix) with ESMTPS id 04C5F1FA5A for ; Mon, 8 Feb 2021 23:54:16 -0500 (EST) Received: from olly by thyestes.tartarus.org with local (Exim 4.92) (envelope-from ) id 1l9KjD-0007pj-81; Tue, 09 Feb 2021 04:34:19 +0000 Date: Tue, 9 Feb 2021 04:34:19 +0000 From: Olly Betts To: David Bremner Subject: Re: out of memory on idle machine Message-ID: <20210209043419.GC19807@survex.com> Mail-Followup-To: David Bremner , Gregor Zattler , notmuch , xapian-discuss@lists.xapian.org References: <20201213131909.GD21521@no.workgroup> <87zh2hhk15.fsf@tethera.net> <20201213141543.GE21521@no.workgroup> <20201213151336.GF21521@no.workgroup> <20201213212252.GH21521@no.workgroup> <20201214192251.GA7858@no.workgroup> <20210130085432.GA14025@no.workgroup> <87bld6shrk.fsf@tethera.net> <20210131081638.GA5640@no.workgroup> <87sg6dweds.fsf@tethera.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <87sg6dweds.fsf@tethera.net> User-Agent: Mutt/1.10.1 (2018-07-13) Message-ID-Hash: UBHOIPLIK4LBB4XV4EVIGS2PZ3JBEULN X-Message-ID-Hash: UBHOIPLIK4LBB4XV4EVIGS2PZ3JBEULN X-MailFrom: olly@survex.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: notmuch , xapian-discuss@lists.xapian.org X-Mailman-Version: 3.2.1 Precedence: list Reply-To: Xapian Discussion List-Id: "Use and development of the notmuch mail system." List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -0.55 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 144.217.243.247 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Queue-Id: 0FA9E9400EA X-Spam-Score: -0.55 X-Migadu-Scanner: scn0.migadu.com X-TUID: e95r+HRX30Oo 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 fixed in 1.4.7 which incorrectly resulted in this error message, but it seems from the quoted text you're using 1.4.11. > I guess you know there are not multiple writers in your setup. There's a lock file locked by fcntl() which protects against multiple writers, so someone/something would have need to have deleted that behind Xapian's back, or else a bug somewhere in the locking code stack. (Aside from that bug, probably the most common case here over time has been that someone deleted the lock file thinking it's "stale", but it's not the mere presence of the file that means the lock is held. It's not at all frequent, but perhaps we should adjust this message to better reflect that.) Have you tried xapian-check on this database? > 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. Yes - 1.4.18 packages are now in Debian testing, so hopefully I can get this done soon. > % xapian-delve -1 -A XDIRECTORY ~/Mail/.notmuch/xapian | sort -u > delve.txt FWIW, the output should be sorted and unique already (sorted by byte order, so equivalent to `LC_ALL=C sort`). Cheers, Olly