linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tavian Barnes <tavianator@tavianator.com>
To: dsterba@suse.cz
Cc: wqu@suse.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: tree-checker: dump the page status if hit something wrong
Date: Tue, 6 Feb 2024 15:19:33 -0500	[thread overview]
Message-ID: <CABg4E-=dZZ=D2HPQjqNJTTkqFOhx=sNzF0sA+J+W71bhH7ZrSQ@mail.gmail.com> (raw)
In-Reply-To: <20240206125114.GN355@twin.jikos.cz>

On Tue, Feb 6, 2024 at 7:51 AM David Sterba <dsterba@suse.cz> wrote:
> On Mon, Feb 05, 2024 at 10:38:07PM -0500, tavianator@tavianator.com wrote:
> > On Sat, 27 Jan 2024 10:18:36 +1030, Qu Wenruo wrote:
>
> > Here's my reproducer if you want to try it yourself.  It uses bfs, a
> > find(1) clone I wrote with multi-threading and io_uring support.  I'm
>
> Do you use other fancy tech like io_uring? This itself can be a
> significant factor, other than config, host etc.

Nothing too fancy.  Actually it's reproducible without io_uring:

    $ make release USE_LIBURING=
    $ ./bin/bfs -j24 /mnt -links 100
    bfs: error:
/mnt/slash/@home/tavianator/code/android/external/honggfuzz/examples/bind/corpus/9fb9c1f611ea4f2a92273d317a872a69.0000021c.honggfuzz.cov:
Structure needs cleaning.
    bfs: error:
/mnt/slash/@home/tavianator/code/android/external/honggfuzz/examples/bind/corpus/9f40657d9a60bac7a329c42339c31397.00004436.honggfuzz.cov:
Structure needs cleaning.
    ...

The fs itself is 4 1TB NVMEs in BTRFS RAID0, stacked on top of LUKS.
The LUKS devices have --perf-no_{read,write}_workqueue enabled.

-- 
Tavian Barnes

  reply	other threads:[~2024-02-06 20:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 23:48 [PATCH] btrfs: tree-checker: dump the page status if hit something wrong Qu Wenruo
2024-02-06  3:38 ` tavianator
2024-02-06  5:54   ` Qu Wenruo
2024-02-06 20:12     ` Tavian Barnes
2024-02-06 20:39       ` Qu Wenruo
2024-02-06 21:48         ` Tavian Barnes
2024-02-06 21:53           ` Qu Wenruo
2024-02-13 18:07             ` Tavian Barnes
2024-02-13 18:26               ` Tavian Barnes
2024-02-13 21:26               ` Qu Wenruo
2024-02-06 21:53           ` Tavian Barnes
2024-02-06 22:01             ` Qu Wenruo
2024-02-06 12:51   ` David Sterba
2024-02-06 20:19     ` Tavian Barnes [this message]
2024-02-06 12:46 ` David Sterba
2024-02-06 20:34   ` Qu Wenruo

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABg4E-=dZZ=D2HPQjqNJTTkqFOhx=sNzF0sA+J+W71bhH7ZrSQ@mail.gmail.com' \
    --to=tavianator@tavianator.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.com \
    /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 NNTP newsgroup(s).