Re: Issuing rollback() due to DESTROY

[Felix Lechner <felix.lechner@lease-up.com>]

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