From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Reindl Harald <h.reindl@thelounge.net>,
Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-btrfs@vger.kernel.org
Subject: Re: BTRF: no free space
Date: Mon, 23 Oct 2023 17:36:24 +1030 [thread overview]
Message-ID: <45a12dcb-c3f0-44f7-9fb6-301d3f060e82@gmx.com> (raw)
In-Reply-To: <78d67a9f-9b9f-436c-884a-9659864d7757@thelounge.net>
On 2023/10/23 17:25, Reindl Harald wrote:
>
>
> Am 22.10.23 um 23:33 schrieb Qu Wenruo:
>> On 2023/10/22 21:13, Reindl Harald wrote:
>>> this is a *new* filesystem and somewhere in the middle of the night at
>>> 10% usage a large rsync stopped because BTRF thinks the filesystem is
>>> full - how is this possible in 2023?
>>>
>>> Metadata, DUP: total=1.00GiB, used=945.61MiB
>>
>> Metadata is already exhausted. Thus no way to start balance.
>
> pervert on a fresh 2 TB filesystem with 200 GB data in 2023 especially
> because i found "btrfs filesystem resize -100M" as solution which worked
> and afterwards balance was possible again
Then this is a little different.
If you can later reclaim space, it means your previous deletion indeed
emptied several data chunks, but they are not removed until cleaner get
kicked in.
Thanks,
Qu
>
> nearly as laughable as a small ext4 filesystem come swith defualts that
> you get a warning it's not useable after 2038
prev parent reply other threads:[~2023-10-23 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 10:43 BTRF: no free space Reindl Harald
2023-10-22 14:50 ` Roman Mamedov
2023-10-22 15:40 ` Reindl Harald
2023-10-22 15:49 ` Roman Mamedov
2023-10-22 21:33 ` Qu Wenruo
2023-10-23 6:55 ` Reindl Harald
2023-10-23 7:06 ` Qu Wenruo [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=45a12dcb-c3f0-44f7-9fb6-301d3f060e82@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=h.reindl@thelounge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.