From: "Hongzhi, Song" <hongzhi.song@windriver.com>
To: <linux-btrfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Nikolay Borisov <nborisov@suse.com>
Cc: <josef@toxicpanda.com>
Subject: Re: Bug?: unlink cause btrfs error but other fs don't
Date: Wed, 4 Sep 2019 16:39:49 +0800 [thread overview]
Message-ID: <bbdb613c-020b-03ec-c218-57299c3f6b29@windriver.com> (raw)
In-Reply-To: <49edadc4-9191-da89-3e3b-ca495f582a4d@windriver.com>
Hi Nikolay,
>
There were multiple fixes from Josef recently improving btrfs enospc
handling with tiny filesystems (which is generally not the targeted use
case of btrfs). The code lives in
https://github.com/kdave/btrfs-devel/commits/misc-next should you want
to test it. Otherwise re-test after next merge windows when those
patches are supposed to be merged for 5.4
>
Thank for your reply, I will keep eyes on the branch.
ps: this email is my simply testcase from ltp
--Hongzhi
On 9/4/19 4:02 PM, Hongzhi, Song wrote:
> Hi ,
>
>
> *Kernel:*
>
> After v5.2-rc1, qemux86-64
>
> make -j40 ARCH=x86_64 CROSS_COMPILE=x86-64-gcc
> use qemu to bootup kernel
>
>
> *Reproduce:*
>
> There is a test case failed on btrfs but success on other
> fs(ext4,ext3), see attachment.
>
>
> Download attachments:
>
> gcc test.c -o myout -Wall -lpthread
>
> copy myout and run.sh to your qemu same directory.
>
> on qemu:
>
> ./run.sh
>
>
> I found the block device size with btrfs set 512M will cause the
> error.
> 256M and 1G all success.
>
>
> *Error info:*
>
> "BTRFS warning (device loop0): could not allocate space for a
> delete; will truncate on mount"
>
>
> *Related patch:*
>
> I use git bisect to find the following patch introduces the issue.
>
> commit c8eaeac7b734347c3afba7008b7af62f37b9c140
> Author: Josef Bacik <josef@toxicpanda.com>
> Date: Wed Apr 10 15:56:10 2019 -0400
>
> btrfs: reserve delalloc metadata differently
> ...
>
>
> Anyone's reply will be appreciated.
>
> --Hongzhi
>
next prev parent reply other threads:[~2019-09-04 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 8:02 Bug?: unlink cause btrfs error but other fs don't Hongzhi, Song
2019-09-04 8:39 ` Hongzhi, Song [this message]
2019-09-04 10:48 ` Josef Bacik
2019-09-05 1:36 ` Hongzhi, Song
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=bbdb613c-020b-03ec-c218-57299c3f6b29@windriver.com \
--to=hongzhi.song@windriver.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nborisov@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;
as well as URLs for NNTP newsgroup(s).