From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-bcachefs@vger.kernel.org, Pavin Joseph <me@pavinjoseph.com>
Subject: Re: Status of rebalance and scrub support
Date: Sat, 17 May 2025 11:12:29 +0200 [thread overview]
Message-ID: <4984817.GXAFRqVoOG@lichtvoll.de> (raw)
In-Reply-To: <c76f1900-de04-422e-b6eb-12453d982ddf@pavinjoseph.com>
Hi.
Pavin Joseph - 17.08.24, 19:17:18 CEST:
> Gentle ping, anyone? 🥺
>
> On 8/7/24 11:07 AM, Pavin Joseph wrote:
> > Hello everyone,
> >
> > Is there an ETA available for full rebalance and scrub support?
I take it that scrub support is not yet fully implemented?
I am not really asking for an ETA – it will be done when it is done –
however I am not sure whether scrub is not yet fully implemented or
whether I am facing a bug:
% bcachefs data scrub /mnt/tmp
Starting scrub on 1 devices: dm-6
device checked corrected uncorrected total
dm-6 0 B 0 B 0 B 17.2 GiB 0% 0 B/sec
(quick test filesystem formatted with bcachefs format without additional
options on LUKS encrypted LVM)
Stays there until I Ctrl-C it. I waited for a bit more than 5 minutes. No
disk I/O to the logical volume.
Self-compiled bcachefs-tools from 1.25.2 tag (displays version 1.25.1
still) on self-compiled kernel 6.14.6 on Devuan Ceres. bcachefs-tools with
tiny patch to Makefile to recognize eudev for determining udev directory.
Best,
--
Martin
next prev parent reply other threads:[~2025-05-17 9:12 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 [this message]
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
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=4984817.GXAFRqVoOG@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-bcachefs@vger.kernel.org \
--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.