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: Fri, 1 Oct 2021 23:46:00 +0000 [thread overview]
Message-ID: <20211001234600.GA28791@dcvr> (raw)
In-Reply-To: <20211001231104.lne6aoq7a5hsqi2e@meerkat.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Fri, Oct 01, 2021 at 10:25:09PM +0000, Eric Wong wrote:
> > export HOME=/tmp/trash # fresh lei/store instance
> > M=87czop5j33.fsf@tynnyri.adurom.net
> > lei import https://yhbt.net/lore/all/$M/t.mbox.gz
> > lei q z:0.. | wc -l # should have all (11) msgs
> > lei q m:$M -t | wc -l # should have the same msgs (11)
>
> Yes, both are reporting 11.
OK, good.
> I'll also be happy to provide the extindex, though that's a bit on the largish
> side at almost 225G. :) Just let me know and I'll see if I can set up a
> temporary VM with access for you.
Probably not needed I wonder if it's related to some
dedupe bugs I also noticed with lei. I'll take a harder look
at it once I get some more calories+sleep in me... I hit some
massive brain fade yesterday-ish working on yhbt :<
If you have extra space somewhere to:
a) copy the old extindex somewhere and do extindex --reindex on it
b) just reindex in place (it /should/ work...)
c) start a new extindex from scratch...
And seeing if inspect gives different results
I'm also running:
public-inbox-extindex --no-fsync /tmp/foo lore/linux-wireless lore/regressions
To create a new extindex with just those two inboxes (and maybe
again with inbox order reversed). But it's also taking a while...
next prev parent reply other threads:[~2021-10-01 23:46 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 [this message]
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
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=20211001234600.GA28791@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).