All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Reindl Harald <h.reindl@thelounge.net>, linux-btrfs@vger.kernel.org
Subject: Re: BTRF: no free space
Date: Mon, 23 Oct 2023 08:03:11 +1030	[thread overview]
Message-ID: <9760a471-6473-4c11-a807-ded4bb2833e2@gmx.com> (raw)
In-Reply-To: <2856c6f2-8d3c-412b-a012-a8151a4b1392@thelounge.net>



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.

>
> -----------------
>
> defaults,noatime,compress-force=zstd:15,ssd,ssd_spread,nodiscard,nobarrier,noexec,nosuid,nodev,commit=60
>
> adding "clear_cache" which solved such issues in the past eve refuses to
> mount it
>
> [root@arrakisvm:~]$ mount /mnt/fileserver-backup/
> mount: /mnt/fileserver-backup: mount(2) system call failed: No space
> left on device.
>
> -----------------
>
> [root@arrakisvm:~]$ df
> Filesystem     Type   Size  Used Avail Use% Mounted on
> /dev/sdd1      btrfs  2.0T  209G     0 100% /mnt/fileserver-backup
>
> [root@arrakisvm:~]$ btrfs fi df /mnt/fileserver-backup
> Data, single: total=1.95TiB, used=207.05GiB

Is this after you deleted some files? Or exactly where the situation is
when the ENOSPC happens?

If it's the latter case, it looks like a kernel bug that we're
over-allocating data chunks, and we need to investigate.
But please provide the initial 'btrfs fi df' output for that case.

If it's the former case and you're trying to make up enough space, I'm
afraid you have to delete more data until one continous 1G chunk is
freed up, then you can do balance to free up most of the space.

Thanks,
Qu

> System, DUP: total=8.00MiB, used=224.00KiB
> Metadata, DUP: total=1.00GiB, used=945.61MiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
>
> [root@arrakisvm:~]$ btrfs balance start -dusage=5 /mnt/fileserver-backup
> ERROR: error during balancing '/mnt/fileserver-backup': No space left on
> device
>
> [root@arrakisvm:~]$ dmesg
> [Sun Oct 22 12:31:52 2023] BTRFS info (device sdd1): balance: start
> -dusage=5
> [Sun Oct 22 12:31:54 2023] BTRFS info (device sdd1): 496 enospc errors
> during balance
> [Sun Oct 22 12:31:54 2023] BTRFS info (device sdd1): balance: ended with
> status: -28
>
>

  parent reply	other threads:[~2023-10-22 21:33 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 [this message]
2023-10-23  6:55   ` Reindl Harald
2023-10-23  7:06     ` Qu Wenruo

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=9760a471-6473-4c11-a807-ded4bb2833e2@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.