From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: Troubleshooting threads missing from /all/
Date: Mon, 18 Oct 2021 05:25:26 +0000 [thread overview]
Message-ID: <20211018052526.M214021@dcvr> (raw)
In-Reply-To: <20211017231245.GA10556@dcvr>
Eric Wong <e@80x24.org> wrote:
> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> > 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.
>
> Btw, I'm chasing a separate bug in v2 which causes recycled
> Message-IDs to go missing sometimes from a v2 over.sqlite3;
> which then causes -extindex to lose a message...
I just pushed out commit 325fbe26c3e7731e
(v2: mirrors don't clobber msgs w/ reused Message-IDs, 2021-10-18)
Now I'm reindexing all my v2 inboxes before running
"-extindex --all --reindex --fast". Fortunately, v2 inboxes
are all "-L basic" so they're not too expensive to reindex.
Really hoping this is the last bug related to indexing for a
while...
next prev parent reply other threads:[~2021-10-18 5:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 13:05 Troubleshooting threads missing from /all/ Konstantin Ryabitsev
2021-10-01 19:58 ` Eric Wong
2021-10-01 20:08 ` Konstantin Ryabitsev
2021-10-01 20:41 ` Eric Wong
2021-10-01 20:49 ` Konstantin Ryabitsev
2021-10-01 20:54 ` Eric Wong
2021-10-01 20:58 ` Konstantin Ryabitsev
2021-10-01 22:25 ` Eric Wong
2021-10-01 22:27 ` Eric Wong
2021-10-01 23:11 ` Konstantin Ryabitsev
2021-10-01 23:46 ` Eric Wong
2021-10-02 0:02 ` Eric Wong
2021-10-05 4:39 ` Eric Wong
2021-10-05 18:03 ` Konstantin Ryabitsev
2021-10-06 10:18 ` Eric Wong
2021-10-07 8:36 ` Eric Wong
2021-10-07 13:57 ` Konstantin Ryabitsev
2021-10-07 21:36 ` Eric Wong
2021-10-07 21:33 ` Eric Wong
2021-10-07 21:33 ` Eric Wong
2021-10-08 17:33 ` Konstantin Ryabitsev
2021-10-08 21:34 ` Eric Wong
2021-10-16 9:43 ` Eric Wong
2021-10-17 18:04 ` Konstantin Ryabitsev
2021-10-17 23:12 ` Eric Wong
2021-10-18 5:25 ` Eric Wong [this message]
2021-10-18 14:04 ` Konstantin Ryabitsev
2021-10-18 14:03 ` Konstantin Ryabitsev
2021-10-24 0:03 ` Eric Wong
2021-10-26 21:11 ` Konstantin Ryabitsev
2021-10-29 10:18 ` release updates [was: Troubleshooting threads missing from /all/] Eric Wong
2021-10-01 20:17 ` Troubleshooting threads missing from /all/ Konstantin Ryabitsev
2021-10-02 11:39 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211018052526.M214021@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).