Re: Issuing rollback() due to DESTROY

[Eric Wong <e@80x24.org>]

Felix Lechner <felix.lechner@lease-up.com> wrote:
> 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?

No, v2 is always better if you have a lot of messages.
v1 was only suited for small archives and I expect debbugs
to be really busy.

> > 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.

OK...

> > I wonder if it was rsync or some dirty shutdown or bad HW of some
> > sort.
> 
> Two back-to-back power outages were responsible.

Ouch, yeah; and looking below it's even worse...

> > 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?

Got backups?

If you have the original mails, then you could probably restore
and reimport the blobs into git (possibly starting with a new
inbox and sharing objects).  You might have to brute force the
trees and commits to get repeatable ordering.

You could probably nuke the Xapian + SQLite DBs and reset the
git history to known point which lacks corrupted objects as
a starting point to speed up the process.

But yeah, there's not much that can be done if git storage is
corrupted aside from reimporting :<

> > 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.

Thanks, I'm worried about electricity use and possible fire
hazards of zappers.  Just bundling up with thick clothing (they
bite through thin layers!) and wearing goggles from now on
despite the heat :<