From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 6B0496DE02A9 for ; Tue, 22 Mar 2016 13:32:53 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.028 X-Spam-Level: X-Spam-Status: No, score=-0.028 tagged_above=-999 required=5 tests=[AWL=-0.017, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aVOIrtEDHEnF for ; Tue, 22 Mar 2016 13:32:45 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 5082C6DE0217 for ; Tue, 22 Mar 2016 13:32:45 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1aiSzN-0001GX-Vb; Tue, 22 Mar 2016 16:33:18 -0400 Received: (nullmailer pid 10208 invoked by uid 1000); Tue, 22 Mar 2016 20:32:40 -0000 From: David Bremner To: Chris Down , notmuch@notmuchmail.org Subject: Re: "The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation" In-Reply-To: <20160322171509.GA2233@chrisdown.name> References: <20160322171509.GA2233@chrisdown.name> User-Agent: Notmuch/0.21+74~g6c60fb1 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Tue, 22 Mar 2016 17:32:40 -0300 Message-ID: <87mvpql0d3.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2016 20:32:53 -0000 Chris Down writes: > After looking around for information about this error, it seems it can also > mean that the Xapian database is corrupted. Since this is happening on two > different databases, it seems interesting that the corruption would happen in > exactly the same way on both. Is there some way to verify the existence or > non-existence of database corruption in a Xapian database that I could try? You could try running xapian-check $MAILDIR/.notmuch/xapian It might be a good idea to make a backup with notmuch dump; this is a read-only operation so it should not make things worse. d