From: Rachel Sibley <rasibley@redhat.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Jan Stancek <jstancek@redhat.com>
Subject: Re: LTP fs_fill test results in BTRFS warning (device loop0): could not allocate space for a delete; will truncate on mount warnings
Date: Sat, 7 Sep 2019 16:26:01 -0400 [thread overview]
Message-ID: <4adcb8d3-3212-7dd8-75a7-d9f1a17deb0c@redhat.com> (raw)
In-Reply-To: <CAJCQCtS0=-9RouGbn-hWKJrUT56mJT=3ij5_wC5jujLwrS95=g@mail.gmail.com>
On 9/6/19 5:56 PM, Chris Murphy wrote:
> On Fri, Sep 6, 2019 at 3:35 PM Chris Murphy <lists@colorremedies.com> wrote:
>> On Fri, Sep 6, 2019 at 1:21 PM Rachel Sibley <rasibley@redhat.com> wrote:
>>> Hello,
>>>
>>> While running LTP [1] as part of CKI [2] testing, we noticed the fs_fill
>>> test fails pretty
>>> consistently with BTRFS warnings seen below, this is seen with recent
>>> kernel (5.2.12).
>>> I have included the logs below for reference.
>> I'm only 6 for 6, but so far can't get it to trigger with 5.3.0-rc7
> Also cannot reproduce, 10 for 10 with 5.2.13-200.fc30.x86_64 which was
> just built in koji, same as 5.2.12 which was quickly replaced with a
> single unrelated revert for touchpads.
>
> But comparing fs_fill logs, yours has a ton more writer threads (~6x)
> and ENOSPC counts. Possibly related?
It could be related to the higher thread/ENOSPC counts, I tried to
manually reproduce
right now and was unsuccessful, I'll see if I can get a reproducible
scenario. I'm traveling
the next few weeks but will review results when I get back.
Thanks for looking into it!
Rachel
>
prev parent reply other threads:[~2019-09-07 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 19:21 LTP fs_fill test results in BTRFS warning (device loop0): could not allocate space for a delete; will truncate on mount warnings Rachel Sibley
2019-09-06 21:35 ` Chris Murphy
2019-09-06 21:56 ` Chris Murphy
2019-09-07 20:26 ` Rachel Sibley [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=4adcb8d3-3212-7dd8-75a7-d9f1a17deb0c@redhat.com \
--to=rasibley@redhat.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=jstancek@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).