From: Nikolay Borisov <nborisov@suse.com>
To: "Hongzhi, Song" <hongzhi.song@windriver.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>, josef@toxicpanda.com
Subject: Re: Bug Report: Btrfs can't allocate space for delete when block size arounds 512M
Date: Wed, 4 Sep 2019 11:03:09 +0300 [thread overview]
Message-ID: <4c4f6620-66e5-8c1f-d894-c9175163bf03@suse.com> (raw)
In-Reply-To: <3eca92d0-5a57-3fff-63e1-edd3217341d5@windriver.com>
On 4.09.19 г. 5:36 ч., Hongzhi, Song wrote:
> Anybody notice this?
>
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
prev parent reply other threads:[~2019-09-04 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b501bcff-8be0-4303-8789-363fda4658e5@windriver.com>
2019-08-02 3:11 ` Bug Report: Btrfs prompts "can't allocate space for delete" " Hongzhi, Song
2019-09-04 2:36 ` Bug Report: Btrfs can't allocate space for delete " Hongzhi, Song
2019-09-04 3:44 ` Hongzhi, Song
2019-09-04 8:03 ` Nikolay Borisov [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=4c4f6620-66e5-8c1f-d894-c9175163bf03@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.com \
--cc=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
all inboxes | Powered by JetHome®