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 CBC606DE1916 for ; Wed, 22 Apr 2015 20:50:14 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.339 X-Spam-Level: X-Spam-Status: No, score=0.339 tagged_above=-999 required=5 tests=[AWL=0.339] 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 0Qz2SxlJdYvd for ; Wed, 22 Apr 2015 20:50:12 -0700 (PDT) Received: from mx.xen14.node3324.gplhost.com (gitolite.debian.net [87.98.215.224]) by arlo.cworth.org (Postfix) with ESMTPS id B37F86DE17BF for ; Wed, 22 Apr 2015 20:50:11 -0700 (PDT) Received: from remotemail by mx.xen14.node3324.gplhost.com with local (Exim 4.80) (envelope-from ) id 1Yl88h-0003wd-Ms; Thu, 23 Apr 2015 03:49:23 +0000 Received: (nullmailer pid 27916 invoked by uid 1000); Thu, 23 Apr 2015 03:49:01 -0000 From: David Bremner To: Mayeu , notmuch@notmuchmail.org Subject: Re: Notmuch removing messages from the index, when calling `new` two times in a row In-Reply-To: <87y4llpiom.fsf@azathoth.devlab.ch> References: <87y4llpiom.fsf@azathoth.devlab.ch> User-Agent: Notmuch/0.19+96~g703c8f9 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Thu, 23 Apr 2015 12:49:01 +0900 Message-ID: <87mw1z8pxu.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.18 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: Thu, 23 Apr 2015 03:50:14 -0000 Mayeu writes: > 3. launching `notmuch new` right after, without having done anything else > on my Maildir folder: > > Cleaned up 5 of 156 directories (1m 9s remaining). > No new mail. Removed 22211 messages. Detected 378 file renames. This message means that notmuch thinks 156 directories have been deleted. Do you have any special mounts / symlinks / file systems that might trigger this? d