Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: DanglingPointer <danglingpointerexception@gmail.com>
To: Todor Ivanov <t.i.ivanov@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid10 rebalance questions
Date: Wed, 31 May 2023 22:48:43 +1000	[thread overview]
Message-ID: <4bd29f45-935d-ef16-9f97-1c48e74a385f@gmail.com> (raw)
In-Reply-To: <CAOv4OrUdSBccOiEk_fW2c8wm9YwfYk2vGZtCwHFj_woXKm5NKg@mail.gmail.com>

Hi Todor,

Have you tried looking at the new documentation? 
https://btrfs.readthedocs.io/en/latest/

Could someone respond to Todor?  Many have similar questions and 
experiences.  Thanks in advance!


On 22/5/23 23:02, Todor Ivanov wrote:
>       Hello,
>
>       We have a debian10 system with 6x16TB in btrfs raid10. In the
> past we hit an issue with lack of space, which we resolved with data
> rebalance, but some questions left unanswered:
>
> https://unix.stackexchange.com/questions/743528/btrfs-snapshot-fails-with-no-space-left
>
> We will be very happy if you can answer or give guidelines for at
> least the following:
>
> - How often should we run btrfs balance? Trying to use some logic and
> looking at https://docs.nvidia.com/networking-ethernet-software/knowledge-base/Configuration-and-Usage/Storage/When-to-Rebalance-BTRFS-Partitions/
> looks like a good example, but this is not for RAID10. How do we
> calculate chunk size correctly and should we alter Device Size beause
> of data duplication?
> - Is it dangerous and should we rebalance metadata as well, having in
> mind we use btrfs-progs v4.20.1, kernel 4.19.0-16-amd64 and btrfs
> raid10? What is an optimal value for musage?
> - What does it mean when "btrfs fi us" is showing a lot of
> "Unallocated" space, and yet we ran into the out of space issue
> (probably on Metadata data - subvolume snapshot), why isn't Metadata
> expanding into that Unallocated space automatically?
>
>
> Kind regards,
> Todor

      reply	other threads:[~2023-05-31 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOv4OrX7kxTMrpE+AdqWo+PCsAGpBkrJ9irr9Xj8ZcRrPTvRoA@mail.gmail.com>
2023-05-22 13:02 ` btrfs raid10 rebalance questions Todor Ivanov
2023-05-31 12:48   ` DanglingPointer [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=4bd29f45-935d-ef16-9f97-1c48e74a385f@gmail.com \
    --to=danglingpointerexception@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=t.i.ivanov@gmail.com \
    /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