Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Nicholas D Steeves <nsteeves@gmail.com>
To: Roman Mamedov <rm@romanrm.net>,
	Ulli Horlacher <framstag@rus.uni-stuttgart.de>
Cc: linux-btrfs@vger.kernel.org
Subject: How to corrupt a btrfs fs [was Re: Fixing a corrupted file system]
Date: Fri, 24 Apr 2026 14:10:17 -0400	[thread overview]
Message-ID: <87jytwtek6.fsf@digitalmercury.freeddns.org> (raw)
In-Reply-To: <20260424174904.385e875f@nvm>

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

Hi,

Roman Mamedov <rm@romanrm.net> writes:

> On Fri, 24 Apr 2026 10:23:00 +0200
> Ulli Horlacher <framstag@rus.uni-stuttgart.de> wrote:
>
>> root@moep:~# btrfs filesystem df /home
>> Data, single: total=95.01GiB, used=54.27GiB
>> System, single: total=32.00MiB, used=16.00KiB
>> Metadata, single: total=1.00GiB, used=293.70MiB
>> GlobalReserve, single: total=80.53MiB, used=0.00B
>> 
>> (How) can I convert /home to DUP for System and Metadata?
>> (/ looks good)
>> 
>
> 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.

Regards,
Nicholas

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  reply	other threads:[~2026-04-24 18:10 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           ` Nicholas D Steeves [this message]
2026-04-24 18:16             ` How to corrupt a btrfs fs [was Re: Fixing a corrupted file system] Roman Mamedov

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=87jytwtek6.fsf@digitalmercury.freeddns.org \
    --to=nsteeves@gmail.com \
    --cc=framstag@rus.uni-stuttgart.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rm@romanrm.net \
    /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