From: David Sterba <dsterba@suse.cz>
To: Naohiro Aota <Naohiro.Aota@wdc.com>
Cc: David Sterba <dsterba@suse.cz>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Subject: Re: [PATCH] btrfs: avoid possible parallel list adding
Date: Mon, 1 Jul 2024 15:50:36 +0200 [thread overview]
Message-ID: <20240701135036.GC21023@twin.jikos.cz> (raw)
In-Reply-To: <oqcpk2hqam7jwhnpzvzgwj5bqcjyqxia65lx6pe5otfraqxx3e@62ean7ayzwt4>
On Mon, Jul 01, 2024 at 01:35:56PM +0000, Naohiro Aota wrote:
> > This commit has landed in several stable trees so we need to get this
> > fixup out quickly. How hard is to hit the problem? It's caught by list
> > corruption detection but this is most likely not enabled on distro
> > kernels so it might go unnoticed.
>
> It surely occurs when I run fstests generic/166 some (~5) times. I don't
> think it's directly related to the workload, though. It always happens when
> it fails to relocate a chunk due to near ENOSPC state. So, I believe it can
> happen easily on such tight space filesystem.
I see, thanks. This can also happen when profiles are converted and
there's not enough chunk space (like with striped profile conversions).
Sounds serious to me, I'll expedite the fix but it will still take like
a week before it's released. Unfortunatelly it affects kernels up to
5.15.x.
prev parent reply other threads:[~2024-07-01 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 4:32 [PATCH] btrfs: avoid possible parallel list adding Naohiro Aota
2024-06-28 5:37 ` Qu Wenruo
2024-06-28 9:56 ` Filipe Manana
2024-06-28 6:02 ` Johannes Thumshirn
2024-06-28 9:45 ` Filipe Manana
2024-07-01 7:14 ` Naohiro Aota
2024-07-01 9:14 ` Filipe Manana
2024-06-28 10:03 ` Filipe Manana
2024-07-01 7:17 ` Naohiro Aota
2024-07-01 13:12 ` David Sterba
2024-07-01 13:35 ` Naohiro Aota
2024-07-01 13:50 ` David Sterba [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=20240701135036.GC21023@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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