From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Josef Bacik <josef@toxicpanda.com>, Chris Mason <clm@fb.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"kernel-team@lists.ubuntu.com" <kernel-team@lists.ubuntu.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>,
Qu Wenruo <wqu@suse.com>, Filipe Manana <fdmanana@suse.com>
Subject: Re: [BUG] btrfs potential failure on 32 core LTP test (fallocate05)
Date: Wed, 30 Jun 2021 10:34:56 +0200 [thread overview]
Message-ID: <30d510db-df48-e499-6e46-bd84c85d4b41@canonical.com> (raw)
In-Reply-To: <57cfa398-8a33-06e2-dfcd-fa959c27ac47@toxicpanda.com>
On 29/06/2021 20:32, Josef Bacik wrote:
> On 6/29/21 2:28 PM, Krzysztof Kozlowski wrote:
>> On 29/06/2021 20:06, Krzysztof Kozlowski wrote:
>>> Minor update - it's not only Azure's. AWS m5.8xlarge and m5.16xlarge (32
>>> and 64 cores) fail similarly. I'll try later also QEMU machines with
>>> different amount of CPUs.
>>>
>>
>> Test on QEMU machine with 31 CPUs passes. With 32 CPUs - failure as
>> reported.
>>
>> dmesg is empty - no error around this.
>>
>> Maybe something with per-cpu variables?
>
> Ah yeah, so since you are further into this than I am, want to give my recent
> batch of fixes a try?
>
> https://github.com/josefbacik/linux/tree/delalloc-shrink
>
> This might actually resolve the problems. If not I'm getting one of our 64cpu
> boxes setup to test this, I also couldn't reproduce it on my smaller local
> machines. Thanks,
I just gave ita try on v5.13 + merge of your branch and it fixes the
issue, at least on QEMU with 32 and 64 CPUs.
Would be good to find the exact commit fixing it to be sure it gets
backported to stables.
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-06-30 8:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 17:00 Krzysztof Kozlowski
2021-06-29 17:20 ` Josef Bacik
2021-06-29 17:25 ` Krzysztof Kozlowski
2021-06-30 11:21 ` [LTP] " Petr Vorel
2021-06-30 11:29 ` Petr Vorel
2021-06-29 17:24 ` Josef Bacik
2021-06-29 17:26 ` Krzysztof Kozlowski
2021-06-29 17:28 ` Josef Bacik
2021-06-29 18:06 ` Krzysztof Kozlowski
2021-06-29 18:28 ` Krzysztof Kozlowski
2021-06-29 18:32 ` Josef Bacik
2021-06-30 8:34 ` Krzysztof Kozlowski [this message]
2021-06-29 20:14 ` Josef Bacik
2021-06-30 6:52 ` Krzysztof Kozlowski
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=30d510db-df48-e499-6e46-bd84c85d4b41@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--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
Powered by JetHome