From: "Hongzhi, Song" <hongzhi.song@windriver.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: <linux-btrfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Bug?: unlink cause btrfs error but other fs don't
Date: Thu, 5 Sep 2019 09:36:31 +0800 [thread overview]
Message-ID: <853d3a5e-6e65-a7d8-df52-e293cad17600@windriver.com> (raw)
In-Reply-To: <20190904104841.nrdocb7smfporu7m@macbook-pro-91.dhcp.thefacebook.com>
On 9/4/19 6:48 PM, Josef Bacik wrote:
> On Wed, Sep 04, 2019 at 04:02:24PM +0800, 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
>> ...
>>
>>
> I meant to reply to this but couldn't find the original thread. The patches I
> wrote for this merge window were to address this issue. Thanks,
>
> Josef
Ok, thank your, I will try to search them.
--Hongzhi
>
prev parent reply other threads:[~2019-09-05 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 8:02 Hongzhi, Song
2019-09-04 8:39 ` Hongzhi, Song
2019-09-04 10:48 ` Josef Bacik
2019-09-05 1:36 ` Hongzhi, Song [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=853d3a5e-6e65-a7d8-df52-e293cad17600@windriver.com \
--to=hongzhi.song@windriver.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome