From: Roman Mamedov <rm@romanrm.net>
To: Nicholas D Steeves <nsteeves@gmail.com>
Cc: Ulli Horlacher <framstag@rus.uni-stuttgart.de>,
linux-btrfs@vger.kernel.org
Subject: Re: How to corrupt a btrfs fs [was Re: Fixing a corrupted file system]
Date: Fri, 24 Apr 2026 23:16:44 +0500 [thread overview]
Message-ID: <20260424231644.2691eee8@nvm> (raw)
In-Reply-To: <87jytwtek6.fsf@digitalmercury.freeddns.org>
On Fri, 24 Apr 2026 14:10:17 -0400
Nicholas D Steeves <nsteeves@gmail.com> wrote:
> > See https://btrfs.readthedocs.io/en/latest/Balance.html
> >
> > btrfs balance start -mprofiles=single -mconvert=dup /home
>
> FYI, I just tried this with linux-6.12.57, btrfs-progs_6.17.1 and it
> corrupted my filesystem. Luckily I only lose this morning's and
> afternoon's work...
>
> I am happy to provide post-mortem debugging info.
This is the correct command and I've used it successfully in the past.
Perhaps there's a new bug in your kernel or progs version. In that case it
would be helpful for developers to see a dmesg of what happened, along with
all the other stuff, such as "filesystem check" (no --repair for now).
--
With respect,
Roman
prev parent reply other threads:[~2026-04-24 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 15:58 Fixing a corrupted file system Amit Shah
2026-04-01 21:21 ` Qu Wenruo
2026-04-02 18:18 ` Amit Shah
2026-04-02 18:32 ` remi
2026-04-02 18:52 ` Amit Shah
2026-04-02 19:07 ` Forza
2026-04-24 8:23 ` Ulli Horlacher
2026-04-24 12:49 ` Roman Mamedov
2026-04-24 18:10 ` How to corrupt a btrfs fs [was Re: Fixing a corrupted file system] Nicholas D Steeves
2026-04-24 18:16 ` Roman Mamedov [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=20260424231644.2691eee8@nvm \
--to=rm@romanrm.net \
--cc=framstag@rus.uni-stuttgart.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=nsteeves@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 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.