From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id QAzINmwqjmRCMQAASxT56A (envelope-from ) for ; Sat, 17 Jun 2023 23:49:33 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id ILjONWwqjmSDcAAAG6o9tA (envelope-from ) for ; Sat, 17 Jun 2023 23:49:32 +0200 Received: from mail.notmuchmail.org (yantan.tethera.net [135.181.149.255]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 0A07C4D5E for ; Sat, 17 Jun 2023 23:49:32 +0200 (CEST) Received: from yantan.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 3A3975F782; Sat, 17 Jun 2023 21:49:29 +0000 (UTC) X-Greylist: delayed 976 seconds by postgrey-1.36 at yantan; Sat, 17 Jun 2023 21:49:27 UTC Received: from mail.bitfolk.com (mail.bitfolk.com [IPv6:2001:ba8:1f1:f019::25]) by mail.notmuchmail.org (Postfix) with ESMTPS id 65C665F42F for ; Sat, 17 Jun 2023 21:49:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strugglers.net; s=alpha; h=Content-Type:MIME-Version:Message-ID:Subject:To: From:Date:In-Reply-To:Content-Transfer-Encoding:References:Sender:Reply-To:Cc :Content-ID:Content-Description:Resent-To; bh=T8ULoQy1EAYIMBvI/2WOWDMO54Xp+rj503uaTUtafVQ=; b=m1cDfh7GQXza3TRORNpYAhgaw/ u32CrWTFxQA/zFtQ+SfLM08dB5aAGeNsVGWvhwQIrAlI3agNTZbC4zzL13nkgABv5lHN3ieAmgTi6 poBcEON/PFxdPr8NF96A9ZKipAte3ELQxhrdjcZNuQBnVdGKWmLhwvXpJQh/7TvoLrZGEIFM6MQSc oNOEKG4UHVL5pwP+VXFfr2TUBrBsI6+UPeNRDBkmmweqGDz1sfv9IrWjdTI3oxca4WHSp2+u1tlp/ Mw3tAg+m1SpoNGF0Tv2T3mXnb1/gsnP4q2B5sjgJTOAuNUG+sBmZCpjBh06kFBqmWpMSixlkroLUN hMC2kNaw==; Received: from andy by mail.bitfolk.com with local (Exim 4.94.2) (envelope-from ) id 1qAdXi-0007JK-Qr for notmuch@notmuchmail.org; Sat, 17 Jun 2023 21:33:10 +0000 Date: Sat, 17 Jun 2023 21:33:10 +0000 From: Andy Smith To: notmuch@notmuchmail.org Subject: "notmuch compact" questions Message-ID: MIME-Version: 1.0 Content-Disposition: inline OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false Message-ID-Hash: MZ4JNO3TU2QZHESTMN3HQ2SNI36NJ6FA X-Message-ID-Hash: MZ4JNO3TU2QZHESTMN3HQ2SNI36NJ6FA X-MailFrom: andy@strugglers.net 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; digests; suspicious-header X-Mailman-Version: 3.3.3 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Country: DE X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1687038572; a=rsa-sha256; cv=none; b=dPUohP82wSnEo+wgutdbjqezzrdAK81jcFUjP/b+ZcLFJ2OPqnR41vn1nENrriWkitg7eq Aj0TdZPyHxh6OYW1eICToDfRl4qcY7QYQlEVge7CrKZ4RVg5BbP2YdDHQCMwhjdcxamH2V Ni6/kzPolPIDt1YKXvVVvhqhGLM4X4K5MlGTTskllp2eZIzAv/THOvV4p1cIEIiRtvFGj1 kt2mkn0HmQD26O6q96DJinGrVL7ancQfI6v2SUCdXF18UMgnHD3/F7Y1SBXgNwVmWrIObK Ae+Lh/2y4vlI1AwjWXAWchJKQmHN0EZczF+ZE5osW6ZyV9NdRVeLt1aJVexibg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=strugglers.net header.s=alpha header.b=m1cDfh7G; dmarc=fail reason="SPF not aligned (relaxed)" header.from=strugglers.net (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 135.181.149.255 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1687038572; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-owner:list-unsubscribe:list-subscribe:list-post:dkim-signature: openpgp:openpgp; bh=I1iNd1AKHuAqdoLRU+xmJuznua93tedYP8Q6jJ8Hd8U=; b=elCur/i/7BIAXT+LxaFX3+Oau1ZgEHBhg+CXBwVBw5D2+8bxPEPtppcJY0QsGto1amBytG KPcDnYTvJp5BMzR1N33holWUtTBjS1YrlD6I9TJ+Jw4zj03bBMq7Gqlq5CeaDJ9Hx2B92K dJWm2Ru0IQCcOi+MupgXY/khW95gqL43LswydMGOHuB4tBs5V5ZPHqrCIONr2TkS3qnhoT LQj8lfngcbfMQw1QQ6RdGwgTmOlPQ3MrCfd6rzhIn8kVgU5y45rVCy4ud+PUquNumQf5v3 HTXmBzpvtDZMXuyKb8WfhmqErDngyGEqzQ+NYlt2DFHnjlb5XcuBarbHNAwWug== Authentication-Results: aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=strugglers.net header.s=alpha header.b=m1cDfh7G; dmarc=fail reason="SPF not aligned (relaxed)" header.from=strugglers.net (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 135.181.149.255 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Scanner: scn0.migadu.com X-Migadu-Spam-Score: -0.77 X-Spam-Score: -0.77 X-Migadu-Queue-Id: 0A07C4D5E X-TUID: SlBbINQp5Fk0 Hi, I'm using v0.31.4 on Debian 11. I have ~3.9 million messages in my archive and the notmuch database currently takes up 85GiB (though actually "only" 51GiB due to btrfs zstd:1 compression). I did remove a few hundred thousand messages from my archive but the space used by the database did not go down at all. If I ran "notmuch compact" should I expect any space to be reclaimed? The manual page says that this builds a new copy of the database and then switches them over. Does that imply that I will need nearly the same amount of space again to perform the compact, until it finishes and the old database is discarded? The manual page says that the new database is built "in a temporary directory". Where is that directory exactly? Is it inside the current notmuch database directory or is it in $TMPDIR? I ask because it looks like I'll need to make sure that there about 50GiB of space available wherever that is. I'm aware that this procedure is going to take a really really long time. If my machine should crash, or the notmuch process runs out of memory or something, will my database be left in a functional state? If I have to reindex it, that is going to take even longer, so I have to think about how much I want what is probably a very marginal amount of space back! Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting