From: Christoph Hellwig <hch@lst.de>
To: Qu Wenruo <wqu@suse.com>
Cc: Christoph Hellwig <hch@lst.de>, David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs/124 assert failure / crash
Date: Tue, 27 Jan 2026 06:25:44 +0100 [thread overview]
Message-ID: <20260127052544.GC24364@lst.de> (raw)
In-Reply-To: <8b0c1232-4e85-4942-8417-78e12982a090@suse.com>
On Tue, Jan 27, 2026 at 03:49:13PM +1030, Qu Wenruo wrote:
>
>
> 在 2026/1/26 15:25, Christoph Hellwig 写道:
>> When running xfstets on btrfs with SCRATCH_DEV_POOL enabled, I the
>> warning below pretty much every time, and then the assert fail crashing
>> the kernel after it (also in the log below) about every second run.
>
> Mind to share the SCRATCH_DEV_POOL details? Especially the size of each
> device.
export SCRATCH_DEV_POOL="/dev/vdc /dev/nvme0n1 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1 /dev/nvme5n1 /dev/nvme6n1"
NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE RA WSAME
...
vdb 0 4096 0 4096 4096 1 none 256 8192 0B
vdc 0 4096 0 4096 4096 1 none 256 8192 0B
nvme0n1 0 4096 0 4096 4096 0 none 1023 128 0B
nvme4n1 0 4096 0 4096 4096 0 none 1023 128 0B
nvme3n1 0 4096 0 4096 4096 0 none 1023 128 0B
nvme6n1 0 4096 0 4096 4096 0 none 1023 128 0B
nvme2n1 0 4096 0 4096 4096 0 none 1023 128 0B
nvme5n1 0 4096 0 4096 4096 0 none 1023 128 0B
nvme1n1 0 4096 0 4096 4096 0 none 1023 128 0B
this does not seem to happen when all devices are the same size,
something I just ried after pasting this.
prev parent reply other threads:[~2026-01-27 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 4:55 btrfs/124 assert failure / crash Christoph Hellwig
2026-01-27 5:19 ` Qu Wenruo
2026-01-27 5:25 ` Christoph Hellwig [this message]
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=20260127052544.GC24364@lst.de \
--to=hch@lst.de \
--cc=dsterba@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.