Xapian recovery after kernel oops

diff --git a/c9/26ae9de7b2587409f9a63ec3937408ce6eb3b9 b/c9/26ae9de7b2587409f9a63ec3937408ce6eb3b9
new file mode 100644 (file)
index 0000000..fa2cf78
--- /dev/null
+++ b/c9/26ae9de7b2587409f9a63ec3937408ce6eb3b9
@@ -0,0 +1,92 @@
+Return-Path: <five9a2@gmail.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 63FF9431FAF\r
+       for <notmuch@notmuchmail.org>; Thu,  9 May 2013 14:58:44 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.915\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.915 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=1, \r
+       FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.614]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id uvdkXrlWcJid for <notmuch@notmuchmail.org>;\r
+       Thu,  9 May 2013 14:58:39 -0700 (PDT)\r
+Received: from mail-ia0-f169.google.com (mail-ia0-f169.google.com\r
+       [209.85.210.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 9C8CD431FAE\r
+       for <notmuch@notmuchmail.org>; Thu,  9 May 2013 14:58:39 -0700 (PDT)\r
+Received: by mail-ia0-f169.google.com with SMTP id k38so1792703iah.28\r
+       for <notmuch@notmuchmail.org>; Thu, 09 May 2013 14:58:39 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+       h=x-received:sender:from:to:subject:user-agent:date:message-id\r
+       :mime-version:content-type;\r
+       bh=OKur6hDcEcBJ7MLpcvAtywJcuAdjNuXZikf5HKj8zvY=;\r
+       b=yNu1wydmF6Qm6OHWo0rwuFrUUk78+VkL4xpWUJtfk4LyYQJX599bKAOc6zgRgs43kE\r
+       5Nqn1BIqWmN3dvhw5C/KF78jvvfyPQ6QuY6NknaJ9MEWKR5S995i5OufbVo3Kt6FCiy0\r
+       QhdTfoNUdm/8adWlWOp7d/y3tlDh1j0aKO7iFfaaxOdP9myjkZoV32WACX8l0nDMVmm8\r
+       j1xZQ72iXJy7OP5Xj+jlLMTzQM9mH96gIKskXPIp0nI2L4uy9fOasMlA6HuGAIDSvpRM\r
+       rOSn3hKEPXQgLNmQA1ua+7pIGJkAej8avcQ53MQ68g7P7P033AWaoHzTh6cToeIzAVy2\r
+       PYfw==\r
+X-Received: by 10.50.110.10 with SMTP id hw10mr10001753igb.55.1368136717938;\r
+       Thu, 09 May 2013 14:58:37 -0700 (PDT)\r
+Received: from localhost (m800436d0.tmodns.net. [208.54.4.128])\r
+       by mx.google.com with ESMTPSA id qs4sm55229igb.10.2013.05.09.14.58.36\r
+       for <notmuch@notmuchmail.org>\r
+       (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+       Thu, 09 May 2013 14:58:37 -0700 (PDT)\r
+Sender: Jed Brown <five9a2@gmail.com>\r
+From: Jed Brown <jed@59A2.org>\r
+To: notmuch <notmuch@notmuchmail.org>\r
+Subject: Xapian recovery after kernel oops\r
+User-Agent: Notmuch/0.15.2+84~gfa8aadf (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-unknown-linux-gnu)\r
+Date: Thu, 09 May 2013 15:58:28 -0600\r
+Message-ID: <87txmb4xyz.fsf@mcs.anl.gov>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Thu, 09 May 2013 21:58:44 -0000\r
+\r
+My laptop had a kernel oops this morning, apparently triggered by\r
+getting bumped (not very hard, actually).  Upon restarting, I have a\r
+corrupt database:\r
+\r
+  $ notmuch search tag:inbox                                                                                                                                 \r
+  A Xapian exception occurred opening database: The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation\r
+\r
+This is with Linux 3.8.11 and btrfs, though nothing else on the file\r
+systems appears to have been affected.\r
+\r
+  $ xapian-check Mail/.notmuch/xapian/\r
+  Database couldn't be opened for reading: DatabaseModifiedError: The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation\r
+  Continuing check anyway\r
+  Cross-checking document lengths between the postlist and termlist tables would use more than 1GB of memory, so skipping that check\r
+  record:\r
+  xapian-check: DatabaseCorruptError: Db block overwritten - are there multiple writers?\r
+\r
+>From the xapian list archives, recovery doesn't look likely.  According\r
+to this mail, it sounds like the commit should have been atomic.\r
+\r
+  http://lists.xapian.org/pipermail/xapian-discuss/2009-September/007126.html\r
+\r
+Is there likely to be any information in my database that would help\r
+track down the reason why the commit was not atomic?  I don't rule out\r
+the possibility that the corruption was entirely the kernel's fault, but\r
+I don't want to leap to conclusions either.\r