From: Rachel Sibley <rasibley@redhat.com>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, Jan Stancek <jstancek@redhat.com>
Subject: LTP fs_fill test results in BTRFS warning (device loop0): could not allocate space for a delete; will truncate on mount warnings
Date: Fri, 6 Sep 2019 15:21:33 -0400 [thread overview]
Message-ID: <4d97a9bb-864a-edd1-1aff-bdc9c8204100@redhat.com> (raw)
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.
Thank you,
Rachel
*
https://artifacts.cki-project.org/pipelines/147783/logs/aarch64_host_1_console.log
8747.237733] LTP: starting fs_fill
[ 8748.085884] EXT4-fs (loop0): mounting ext2 file system using the ext4
subsystem
[ 8748.103546] EXT4-fs (loop0): mounted filesystem without journal.
Opts: (null)
[ 8751.856179] EXT4-fs (loop0): mounting ext3 file system using the ext4
subsystem
[ 8751.882784] EXT4-fs (loop0): mounted filesystem with ordered data
mode. Opts: (null)
[ 8759.496036] EXT4-fs (loop0): mounted filesystem with ordered data
mode. Opts: (null)
[ 8768.360525] XFS (loop0): Mounting V5 Filesystem
[ 8768.368464] XFS (loop0): Ending clean mount
[ 8775.694012] XFS (loop0): Unmounting Filesystem
[ 8776.179816] BTRFS: device fsid 3f8f3f1f-6293-40c4-91f4-bfe1d5c4451d
devid 1 transid 5 /dev/loop0
[ 8776.190118] BTRFS info (device loop0): disk space caching is enabled
[ 8776.195513] BTRFS info (device loop0): has skinny extents
[ 8776.200927] BTRFS info (device loop0): flagging fs with big metadata
feature
[ 8776.212841] BTRFS info (device loop0): checking UUID tree
[ 9062.793701] BTRFS warning (device loop0): could not allocate space
for a delete; will truncate on mount
[ 9062.794100] BTRFS warning (device loop0): could not allocate space
for a delete; will truncate on mount
<snip>
[ 9062.794172] BTRFS warning (device loop0): could not allocate space
for a delete; will truncate on mount
fs_fill log: https://paste.fedoraproject.org/paste/368EirX-AHSsZhG4Zutm2w
[1] https://github.com/linux-test-project/ltp
[2] https://cki-project.org/
<https://projects.engineering.redhat.com/secure/ViewProfile.jspa?name=jstancek>
next reply other threads:[~2019-09-06 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 19:21 Rachel Sibley [this message]
2019-09-06 21:35 ` LTP fs_fill test results in BTRFS warning (device loop0): could not allocate space for a delete; will truncate on mount warnings Chris Murphy
2019-09-06 21:56 ` Chris Murphy
2019-09-07 20:26 ` Rachel Sibley
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=4d97a9bb-864a-edd1-1aff-bdc9c8204100@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 \
/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).