From 0c2b008161bfc82d5bcf1cf7a3ab4df0d097103d Mon Sep 17 00:00:00 2001 From: =?utf8?q?Amadeusz=20=C5=BBo=C5=82nowski?= Date: Wed, 26 Aug 2015 07:31:34 +0100 Subject: [PATCH] Re: muchsync files renames --- ae/58394adaaf1d93d99d11d7c92d7d3697ac2ece | 136 ++++++++++++++++++++++ 1 file changed, 136 insertions(+) create mode 100644 ae/58394adaaf1d93d99d11d7c92d7d3697ac2ece diff --git a/ae/58394adaaf1d93d99d11d7c92d7d3697ac2ece b/ae/58394adaaf1d93d99d11d7c92d7d3697ac2ece new file mode 100644 index 000000000..35b3ee0fe --- /dev/null +++ b/ae/58394adaaf1d93d99d11d7c92d7d3697ac2ece @@ -0,0 +1,136 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by arlo.cworth.org (Postfix) with ESMTP id 9ABD56DE02C9 + for ; Tue, 25 Aug 2015 23:31:49 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at cworth.org +X-Spam-Flag: NO +X-Spam-Score: -0.004 +X-Spam-Level: +X-Spam-Status: No, score=-0.004 tagged_above=-999 required=5 tests=[AWL=0.097, + DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] + 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 Wh8xRLMvV0C6 for ; + Tue, 25 Aug 2015 23:31:47 -0700 (PDT) +Received: from jim.zolnowski.name (jim.zolnowski.name [188.116.54.122]) + by arlo.cworth.org (Postfix) with ESMTPS id 2037E6DE0275 + for ; Tue, 25 Aug 2015 23:31:46 -0700 (PDT) +DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; + d=aidecoe.name; s=jim; + h=Content-Type:MIME-Version:Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From; bh=xGP0TkFB51VkcC4GYe+h/ZYmtjQ1DEnx18zBJA9Zyoo=; + b=hUAQSPw9GWowCntPo7PPYWjZc4o5XVxhkD/LYchdcQJ255rY/i+fs9C30gi2XHCqNstumerF5UEUOSocHRMA+jQ2Js/2erQRrBKYG/v0YXwnCyRVQUD6ij/bukywYDmVUJGVrbRG5BUONn9JuRexCXEF5J28YlFT6d/59s+9LVguTlIVrERbZprqZEqoeSbOmrMnGrxgIT0EzjDLLlJKOOiiT75pBioKEYABhctnzc6iINvbpxZbD/Ao4gOe8gHDlxzacAtRyJY2Dla3oZbLoM6mlo+uhIh2EdrzzTpWuV32p86Tf0z+5p2rOtd1fWCt7xOzwSpZdWg9WQ4Kind1wg==; +Received: from cpc3-cmbg17-2-0-cust294.5-4.cable.virginm.net ([86.22.65.39] + helo=localhost) + by jim.zolnowski.name with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) + (Exim 4.85) (envelope-from ) + id 1ZUUFJ-0008Ub-D4; Wed, 26 Aug 2015 08:31:41 +0200 +From: Amadeusz =?utf-8?B?xbtvxYJub3dza2k=?= +To: David Mazieres expires 2015-11-21 PST + +Subject: Re: muchsync files renames +In-Reply-To: <87oahxojlv.fsf@ta.scs.stanford.edu> +References: <878u93ujdo.fsf@freja.aidecoe.name> + <876146o920.fsf@ta.scs.stanford.edu> <871teu8kdd.fsf@freja.aidecoe.name> + <87oahxojlv.fsf@ta.scs.stanford.edu> +User-Agent: Notmuch/0.20.2 (http://notmuchmail.org) Emacs/24.5.1 + (x86_64-pc-linux-gnu) +Date: Wed, 26 Aug 2015 07:31:34 +0100 +Message-ID: <87y4gyftmh.fsf@freja.aidecoe.name> +MIME-Version: 1.0 +Content-Type: multipart/signed; boundary="=-=-="; + micalg=pgp-sha512; protocol="application/pgp-signature" +Cc: notmuch@notmuchmail.org +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: Wed, 26 Aug 2015 06:31:49 -0000 + +--=-=-= +Content-Type: text/plain; charset=utf-8 +Content-Transfer-Encoding: quoted-printable + +Hi David, + +(Resending, because I forgot to Cc mailing list.) + +David Mazieres writes: +>> 3. I run muchsync SERVER. +>> 4. When it lasted much longer then initialization I canceled it by +>> single SIGINT (^c). +> +> Interesting. I wish I knew why this was taking much longer than running +> it on the server, and whether the delay was caused by client activity or +> server activity. + +I think there was something happening on server side because with --noup +it has been completed in few seconds. + + > I don't suppose you'd be willing to make a copy of your mail database + > to repeat the experiment without any risk of messing up your real + > maildir? + +I would try it, but unfortunately I would have to make a bit more space +for having second copy of my mail. I am testing muchsync on the same +machine between different users home directories, so it already takes +some space. I'll try the experiment some day this week, I hope. + +>> 5. I rerun muchsync SERVER and then it notified me that notmuch +>> identified files names changes - more than 1000. +> +> Were the link changes on the client (sent) or the server (received) +> side? + +On the server side. That's why I am worried. + + +> I don't think that will change things. maildir.synchronized_flags +> will make things slower, but it shouldn't affect the SUMMARY numbers +> you see at the end of muchsync, other than maybe files moving from +> .../new to .../cur. But presumably most of your mail files were +> already in cur directories. + +So what would happen on my machine is that first client initialization +took place. During this stage muchsync moved some files from new/ to +cur/. Later running "muchsync SERVER" tried to reflect client changes on +server by pushing renames requests to server. Is it what actually could +happend? + + +=2D-=20 +Amadeusz =C5=BBo=C5=82nowski + +--=-=-= +Content-Type: application/pgp-signature; name="signature.asc" + +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.1 + +iQJ8BAEBCgBmBQJV3V1HXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w +ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCMzcyRTFENjI5NUM1MzYwQTQwODQyRUZD +QkNDODAyM0Y1OUUxNzA0AAoJEMvMgCP1nhcE8u8P/jKjYUg1yhZSps+PPQB8BSnY +REdm/QK/CHsmGnY5jAa1OvoAHK23hh1xxeb+4H88AqygGE/1LpPZVm3caBaj4a97 +QwOWrB1vPMfor38ZVw8oPOYT0hwSgpazYOSMp3biDE7wxnh0e5zVxq1AOratgvR7 +Viaqdjc/c+AtfvFemSip2voxT5kbuJbjPKN4Ai2+FBIh3swgfa14UpphWm2Wa94r +hseBA/gqCAiGAH8y3CRUPkQAxctg0T7sWSybBRU+1puHLAvRrkNkXDSj/5TTvbKq +rmGW9CrpxPBOA3g4QzS8cs22cpQ6pDqr2hWUzKgb+vYmzWBUM/f1PvXin/IC4bCT +T3lixs1t7vvcPl7EPGiVGe6d+c1xdSnCriHsMJSwfTDwT95o/bm0kK3WDXNElt3M +QvrE5j20ZYP4KrNjNBJrCOBetXOgIdgzLmTYAoJMw72lCCRqtf+f3A42MUf/HPNC +qz/6wQrrN7DN4UcAziWcpmY7P+C+RJ5vrKirq+mxwKlpy78ceu64Jz8918L182yH +pLVOPzKjvIdiQ57Xi5VP32AzYogEFmpI4dNe4rcVGuUwY7f01+lqhgZUDi2rH0Tn +ObbFW+KWtL3ysEpgDFKFY5MUJ++FzmjM+RUOHfS+pXkVSvChBDr0lV5sbDUY08X+ +OfmYyT6a4ZSIt0nEc2fB +=zaT+ +-----END PGP SIGNATURE----- +--=-=-=-- -- 2.26.2