On Sat, Oct 16, 2021 at 09:43:24AM +0000, Eric Wong wrote: > Eric Wong <e...@80x24.org> wrote: > > Yes. Though given the current situation with missing messages > > from /all/, I'd wait until a reindex recovers the missing > > messages (and probably a fast fsck checker). > > I think "public-inbox-extindex --reindex --all --fast" is > reasonably ready as an fsck checker. I've been running it a > bunch in recent days/weeks and also found+fixed some other bugs > along the way.
Thanks, Eric! I've been out this week for some family time (it was Thanksgiving in Canada), which is why I was staying conspicuously silent. :) I'll give --reindex --fast a whirl in the next few days. > With --fast, --reindex takes around 20 minutes for me with > "--batch-size=20m --no-fsync". The first run may take longer > if it has stuff to do. But running it repeatedly should not > cause it to complain about unseen/stale/mismatched messages > (likely the first run will). > > So it's not /really/ fast, but compared to ~35 hours w/o --fast, > then it's alright. Either way, --reindex should be safe > with parallel -index and -extindex being run by cronjobs. Absolutely, thanks for working on this. -K
