From: Josef Bacik <josef@toxicpanda.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 4.13: No space left with plenty of free space (/home/kernel/COD/linux/fs/btrfs/extent-tree.c:6989 __btrfs_free_extent.isra.62+0xc2c/0xdb0)
Date: Fri, 8 Sep 2017 15:57:19 -0400 [thread overview]
Message-ID: <20170908195718.pxtff7anbvj2kh2g@destiny> (raw)
In-Reply-To: <7459bb074e417c066b525d832d8006ca@wpkg.org>
On Fri, Sep 08, 2017 at 01:33:43PM +0900, Tomasz Chmielewski wrote:
> Just got this one in dmesg with btrfs RAID-1 on top of Linux software
> RAID-5.
>
> Why does it say "No space left" if we have 9 TB free there?
>
We've exhausted the global reserve. I have a patch that I'm pretty sure fixes
this problem, would you mind trying
git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git btrfs-readdir
You need to make sure you are on the btrfs-readdir branch, and that you have the
patch entitled
Btrfs: only check delayed ref usage in should_end_transaction
If you still see the problem let me know, I really want to nail this issue down
and haven't been able to reproduce locally. Thanks,
Josef
prev parent reply other threads:[~2017-09-08 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 4:33 4.13: No space left with plenty of free space (/home/kernel/COD/linux/fs/btrfs/extent-tree.c:6989 __btrfs_free_extent.isra.62+0xc2c/0xdb0) Tomasz Chmielewski
2017-09-08 4:56 ` Tomasz Chmielewski
2017-09-08 12:45 ` Tomasz Chmielewski
2017-09-08 11:02 ` Peter Grandi
2017-09-08 19:57 ` Josef Bacik [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=20170908195718.pxtff7anbvj2kh2g@destiny \
--to=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mangoo@wpkg.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).