Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Reindl Harald <h.reindl@thelounge.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRF: no free space
Date: Sun, 22 Oct 2023 20:49:17 +0500	[thread overview]
Message-ID: <20231022204917.7744389f@nvm> (raw)
In-Reply-To: <62e47536-671a-4ef1-a703-27be2692b124@thelounge.net>

On Sun, 22 Oct 2023 17:40:05 +0200
Reindl Harald <h.reindl@thelounge.net> wrote:

> >> [root@arrakisvm:~]$ btrfs fi df /mnt/fileserver-backup
> >> Data, single: total=1.95TiB, used=207.05GiB
> >> System, DUP: total=8.00MiB, used=224.00KiB
> >> Metadata, DUP: total=1.00GiB, used=945.61MiB
> >> GlobalReserve, single: total=512.00MiB, used=0.00B
> > 
> > 1) Report your kernel version
> 
> 6.5.7-100.fc37.x86_64
> 
> > 2) Retry without "ssd" and especially without "ssd_spread". The weird thing
> > here is that it appears the FS has allocated the entire unused space as "data"
> > chunks, leaving no space for any new metadata chunk. Personally I don't have
> > any other guess for the cause aside from the rarely-used (and little-tested?)
> > ssd_spread option. Of course still a bug even if so.
> 
> no - it allocated METADATA
> Metadata, DUP: total=1.00GiB, used=945.61MiB

In your output I see that 1.95 TB was allocated for data chunks, even if only
207 GB of those are used for actual data. My guess was that this was
preventing the creation of one more metadata chunk when it was needed, which
broke everything.


-- 
With respect,
Roman

  reply	other threads:[~2023-10-22 15:49 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 [this message]
2023-10-22 21:33 ` Qu Wenruo
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=20231022204917.7744389f@nvm \
    --to=rm@romanrm.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox