From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Christoph Anton Mitterer <calestyo@scientia.org>,
linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC while df shows 826.93GiB free
Date: Tue, 7 Dec 2021 11:29:57 +0800 [thread overview]
Message-ID: <b7b6a6a7-700e-f83d-dae6-581ed6befbef@gmx.com> (raw)
In-Reply-To: <c64be50bdc99b993b910a7ab019af8d552eeb0d4.camel@scientia.org>
On 2021/12/7 11:06, Christoph Anton Mitterer wrote:
> On Tue, 2021-12-07 at 10:59 +0800, Qu Wenruo wrote:
>>
>> Since your metadata is already full, you may need to delete enough
>> data
>> to free up enough metadata space.
>>
>> The candidates includes small files (mostly inlined files), and large
>> files with checksums.
>
> On that fs, there are rather many large files (800MB - 1.5 GB).
>
> Is there anyway to get (much?) more space reserved for metadata in the
> future respectively on the other existing filesystems that haven't
> deadlocked themselves yet?!
In fact, this is not really a deadlock, only balance is blocked by such
problem.
For other regular operations, you either got ENOSPC just like all other
fses which runs out of space, or do it without problem.
Furthermore, balance in this case is not really the preferred way to
free up space, really freeing up data is the correct way to go.
Thanks,
Qu
>
>
> Thanks,
> Chris.
>
next prev parent reply other threads:[~2021-12-07 3:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 2:29 ENOSPC while df shows 826.93GiB free Christoph Anton Mitterer
2021-12-07 2:59 ` Qu Wenruo
2021-12-07 3:06 ` Christoph Anton Mitterer
2021-12-07 3:29 ` Qu Wenruo [this message]
2021-12-07 3:44 ` Christoph Anton Mitterer
2021-12-07 4:56 ` Qu Wenruo
2021-12-07 14:30 ` Christoph Anton Mitterer
2021-12-07 7:21 ` Zygo Blaxell
2021-12-07 12:31 ` Jorge Bastos
2021-12-07 15:07 ` Christoph Anton Mitterer
2021-12-07 18:14 ` Zygo Blaxell
2021-12-16 23:16 ` Christoph Anton Mitterer
2021-12-17 2:00 ` Qu Wenruo
2021-12-17 3:10 ` Christoph Anton Mitterer
2021-12-17 5:53 ` Zygo Blaxell
2021-12-07 15:10 ` Jorge Bastos
2021-12-07 15:22 ` Christoph Anton Mitterer
2021-12-07 16:11 ` Jorge Bastos
2021-12-07 15:39 ` Phillip Susi
2021-12-16 3:47 ` Christoph Anton Mitterer
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=b7b6a6a7-700e-f83d-dae6-581ed6befbef@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=calestyo@scientia.org \
--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).