public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell Haley <yumpusamongus@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS corruption after conversion to block group tree
Date: Sun, 3 Dec 2023 06:16:21 -0600	[thread overview]
Message-ID: <e78b13ac-6fdf-48eb-b33a-82474e49003d@gmail.com> (raw)
In-Reply-To: <39ff2b14-9f8a-4477-aa49-b4cb19e1d7ef@gmail.com>



On 12/3/23 06:05, Russell Haley wrote:
> 
> 
> On 12/2/23 00:43, Qu Wenruo wrote:
>>
>> Very hard to say if it's the firmware's fault, but it can also be our
>> fault on the bg tree conversion.
>>
>> Anyway two reports are more than enough for us to enhance bg tree
>> conversion code.
>>
> 
> If the two reports you're counting are mine and Alexander's from October
> that I linked at the top of the thread, make it three:
> 
> https://www.reddit.com/r/btrfs/comments/186pw3v/fs_got_corrupted_after_running_btrfstune/

Might be 4.  A user in that thread says they had the same issue after
doing that and posted about it last week, but I tracked back to their
older thread:

https://www.reddit.com/r/btrfs/comments/17si8cb/cannot_mount/

They didn't mention block group tree conversion the first time, so they
misremembered at least once.

Thanks,

- Russell Haley

      reply	other threads:[~2023-12-03 12:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 11:46 BTRFS corruption after conversion to block group tree Russell Haley
2023-12-01 20:09 ` Qu Wenruo
2023-12-02  2:45   ` Russell Haley
2023-12-02  4:13     ` Qu Wenruo
2023-12-02  4:25       ` Qu Wenruo
2023-12-02  6:13         ` Russell Haley
2023-12-02  6:43           ` Qu Wenruo
2023-12-02  8:04             ` Russell Haley
2023-12-02  9:00               ` Qu Wenruo
2023-12-03 12:05             ` Russell Haley
2023-12-03 12:16               ` Russell Haley [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=e78b13ac-6fdf-48eb-b33a-82474e49003d@gmail.com \
    --to=yumpusamongus@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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