From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.6 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 1EBFD1F670 for ; Sun, 17 Oct 2021 18:04:54 +0000 (UTC) Received: by mail-qt1-x82e.google.com with SMTP id r17so13409833qtx.10 for ; Sun, 17 Oct 2021 11:04:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=gzr0jqv/PfEeMByF/PodH3HCdjpQuMgjbHP1IbJUZ44=; b=Gk1OYBadB/yO47rZRyHTgL3nTW/Ye3KIZRn8On1rvFZEv/676WHv/fbreU3FGa/EVM 527JSrkUrB+pJXzMvM4MnGirRlPap2Dd2GncjvyQEXHmfZXoXQ+/Yuz0KkZTR0HS6uEC xAkboRPjmNI/Jc1fE+e4NngcUD9SEjP7Iqb8E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=gzr0jqv/PfEeMByF/PodH3HCdjpQuMgjbHP1IbJUZ44=; b=lljcqwOedoQlVTiiuMACrpPBBoFXKaWednmIgE7Nz3blT7xgUnQQbQxz5WbpAWrK6z zfKsuABsmlHBC2lsAZn1wVkst9XtmRCLDraLZ/tM/6fw2uF2kO5AMzshkYDJbL18GOnT 8WL5EmyiwPhMZs0ZcWTMNreTtIXVKniCkTbjxPYrIpkBCFy62Mot/mkO0qwncmeuoeX+ y4FaNQUxVZ3dAwTYte+NH4bwcKFDwFeiTWD7ubrKnpN5HluManEaZ3PT5oUxYF2ev39Y ZiUQBgfYqWg/ewwvPc20iMvKLkIDmdwWOsS7RP5/pzc9TpV8KxlJZl/K6iaOOhOPGJ6d RqXg== X-Gm-Message-State: AOAM533oRnNCorodY20VKQ35OgwbjsmE5d+jNFU7ueuZjykLmqW8WJ2E GZggY+TKIagOuvgpH5IsSs3j8g== X-Google-Smtp-Source: ABdhPJzax3IzytK9tlpklxDEXY3EZOIHhnUcpIxX8ly4xoW7Eg3EA6gXJv7s3TPB/dfVt+uOeYXQzA== X-Received: by 2002:ac8:5f54:: with SMTP id y20mr25528918qta.324.1634493892508; Sun, 17 Oct 2021 11:04:52 -0700 (PDT) Received: from nitro.local (bras-base-mtrlpq5031w-grc-32-216-209-220-181.dsl.bell.ca. [216.209.220.181]) by smtp.gmail.com with ESMTPSA id u3sm5404661qkj.53.2021.10.17.11.04.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 17 Oct 2021 11:04:51 -0700 (PDT) Date: Sun, 17 Oct 2021 14:04:50 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Troubleshooting threads missing from /all/ Message-ID: <20211017180450.e6zsbbx2at2rggxx@nitro.local> References: <20211001205817.y2h3xypudngkttkj@meerkat.local> <20211001222509.GA1968@dcvr> <20211001231104.lne6aoq7a5hsqi2e@meerkat.local> <20211001234600.GA28791@dcvr> <20211005043954.GA23990@dcvr> <20211005180324.3miboond7ubth5v5@meerkat.local> <20211007213307.29376-0@dcvr> <20211008173336.ftokrvr73vcuhtpg@meerkat.local> <20211008213433.M867097@dcvr> <20211016094324.GA16488@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20211016094324.GA16488@dcvr> List-Id: On Sat, Oct 16, 2021 at 09:43:24AM +0000, Eric Wong wrote: > Eric Wong 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