From: Martin Steigerwald <martin@lichtvoll.de>
To: John Stoffel <john@stoffel.org>,
Kent Overstreet <kent.overstreet@linux.dev>
Cc: "Malte Schröder" <malte.schroeder@tnxip.de>,
"Pavin Joseph" <me@pavinjoseph.com>,
linux-bcachefs@vger.kernel.org
Subject: Re: Status of rebalance and scrub support
Date: Mon, 19 May 2025 17:29:38 +0200 [thread overview]
Message-ID: <3362164.44csPzL39Z@lichtvoll.de> (raw)
In-Reply-To: <wqlurfdcgogbxneenl4dbu756x3qy5oez3thyp5ifjb2n326md@ixrcqjntrzc2>
Kent Overstreet - 19.05.25, 16:54:17 CEST:
> > >> If by "rebalance" you mean equalize the amount of data between
> > >> drives
> > >> (like btrfs): No, it can't do that at the moment. There is a thing
> > >> called rebalance on bcachefs, but it does something different (I
> > >> think
> > >> it moves data between tiers).
> > >
> > > I was thinking about renaming "rebalance" to "background_data".
> >
> > tier_migrate? migrate?
>
> It's not just for migrating to different devices, background compression
> is quite popular.
How about "background_data" as new command group (maybe you meant it this
way to begin with)? Like in:
- background_data migrate
- background_data compression
Only caveat is: It is a bit lengthy this way.
Maybe there is a good shortcut for "background_data" like "bg_data" or an
alternative word for it that is short but also matches the meaning. But
maybe these are more rare command calls and then length may not really
matter.
Best,
--
Martin
prev parent reply other threads:[~2025-05-19 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 5:37 Status of rebalance and scrub support Pavin Joseph
2024-08-17 17:17 ` Pavin Joseph
2025-05-17 9:12 ` Martin Steigerwald
2025-05-17 9:15 ` Malte Schröder
2025-05-17 10:41 ` Martin Steigerwald
2025-05-17 12:18 ` Pavin Joseph
2025-05-17 12:21 ` Malte Schröder
2025-05-17 15:04 ` Kent Overstreet
2025-05-19 14:43 ` John Stoffel
2025-05-19 14:54 ` Kent Overstreet
2025-05-19 15:00 ` John Stoffel
2025-05-19 15:29 ` Martin Steigerwald [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=3362164.44csPzL39Z@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=john@stoffel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=malte.schroeder@tnxip.de \
--cc=me@pavinjoseph.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 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.