From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS396097 208.82.96.0/21 X-Spam-Status: No, score=-2.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,SPF_HELO_NONE, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from sail-ipv4.us-core.com (sail-ipv4.us-core.com [208.82.101.137]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id A4F43D48C9 for ; Fri, 21 Jun 2024 16:03:12 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; secure) header.d=lease-up.com header.i=@lease-up.com header.a=rsa-sha256 header.s=2017 header.b=AGWZQC5Y; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; s=2017; bh=VkNIYJTRcztRO3i k2mNygaLFi6QwRqH5eMDgcBN6V0s=; h=date:references:in-reply-to:subject: cc:to:from; d=lease-up.com; b=AGWZQC5YKr3hf8zcxkRvwBaTX0FfR6MJIOFtb0/w CSDaps1YbOa1jqTt6Yw5wRb4tlTHUy4EI8p4NQAC130yJbDLA6i2k11XngxUrzJan7+ZHZ MnYPY0KzfnSExRdXaNshgAMDPDxiwVKrO2+JqCrITXxAWEv5/8Gijvuire4Q8= Received: by sail-ipv4.us-core.com (OpenSMTPD) with ESMTPSA id 196e0fa3 (TLSv1.3:TLS_CHACHA20_POLY1305_SHA256:256:NO); Fri, 21 Jun 2024 16:03:06 +0000 (UTC) From: Felix Lechner To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Issuing rollback() due to DESTROY In-Reply-To: <20240618023953.M696062@dcvr> References: <87sey2q4b3.fsf@lease-up.com> <20240527225154.M531684@dcvr> <87plt6psfv.fsf@lease-up.com> <20240528141159.M33494@dcvr> <87le33dvct.fsf@lease-up.com> <20240618023953.M696062@dcvr> Date: Fri, 21 Jun 2024 09:03:06 -0700 Message-ID: <87ed8qi8qt.fsf@lease-up.com> MIME-Version: 1.0 Content-Type: text/plain List-Id: Hi Eric, On Tue, Jun 18 2024, Eric Wong wrote: > msgmap.sqlite3 is more important if you're using v2, the > uncommon altid feature, or broken messages with multiple > Message-IDs; but it's unlikely important for v1 inboxes. I use v2. Should I still be using v1? > Wait, I hope you're not rsync-ing into an inbox directory > containing SQLite files. No. I am not doing that. The rsync process sends a email, which is then filed by my MTA. > I wonder if it was rsync or some dirty shutdown or bad HW of some > sort. Two back-to-back power outages were responsible. > if you delete all the SQLite and Xapian files, you should be able to > run `public-inbox-index' on that directory and it'll recreate it. Thank you for that advice. Unfortunately, that results in the following error messages: $ public-inbox-index public-inbox/lists/debbugs-state-changes-rsync.git/ error: object file /srv/patchwise/public-inbox/lists/debbugs-state-changes-rsync.git/git/0.git/objects/58/7ba7ce7f8dd9c65a711c9d8442c77e76bc6246 is empty error: object file /srv/patchwise/public-inbox/lists/debbugs-state-changes-rsync.git/git/0.git/objects/58/7ba7ce7f8dd9c65a711c9d8442c77e76bc6246 is empty fatal: bad object 587ba7ce7f8dd9c65a711c9d8442c77e76bc6246 git log failed: $?=32768 at /gnu/store/infi869byszi6cvvp6wcd7n431pd4zlh-public-inbox-1.9.0/lib/perl5/site_perl/5.36.0/PublicInbox/SearchIdx.pm line 967. [1]: (in cleanup) 11336 shard[1] xdb not released [2]: (in cleanup) 11337 shard[2] xdb not released [0]: (in cleanup) 11335 shard[0] xdb not released Is there a way to fix the Git repo? > Nope. It's a disaster :< Bug zappers and mosquito nets are commonly available where I live. Please let me know if I should send links with purchasing information. Also, thanks for your help so far! Kind regards Felix