Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Forza <forza@tnonline.net>
To: remi@georgianit.com, Qu Wenruo <wqu@suse.com>,
	Amit Shah <amit@infradead.org>,
	linux-btrfs@vger.kernel.org
Subject: Re: Fixing a corrupted file system
Date: Thu, 2 Apr 2026 21:07:01 +0200 (GMT+02:00)	[thread overview]
Message-ID: <87d1aca.ae41f579.19d4f977d95@tnonline.net> (raw)
In-Reply-To: <571fb6a8-d4e7-42ed-9f19-22962163918d@app.fastmail.com>



---- From: remi@georgianit.com -- Sent: 2026-04-02 - 20:32 ----

> 
> 
> On Wed, Apr 1, 2026, at 5:21 PM, Qu Wenruo wrote:
> 
>>
>> Nope, btrfs will only try extra mirrors, but in your case your metadata 
>> doesn't even have extra mirrors.
>> Which is not common, as the default btrfs mkfs profiles will go DUP for 
>> metadata.
> 
> I forget what mkfs version, but the default behaviour changed a few years ago so the default profile is Single on SSD's. (Correct me if this has since been reverted.)  Something about the way SSD's copy on write, the DUP entries would end up on the same physical block, so the redundancy was not effective.
> 

It is the reverse. Since btrfs-progs 5.15, the default was changed to DUP for single device fs.

https://github.com/kdave/btrfs-progs/commit/65181c273e67bd48d01fc79f00826dce38b93c4c

~ Forza


  parent reply	other threads:[~2026-04-02 19:07 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 [this message]
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

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=87d1aca.ae41f579.19d4f977d95@tnonline.net \
    --to=forza@tnonline.net \
    --cc=amit@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=remi@georgianit.com \
    --cc=wqu@suse.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