public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Kent Overstreet <kent.overstreet@linux.dev>
Subject: Re: bcachefs: do not run 6.7: upgrade to 6.8 immediately if you have a multi device fs
Date: Fri, 15 Mar 2024 09:57:34 +0100	[thread overview]
Message-ID: <12416320.O9o76ZdvQC@lichtvoll.de> (raw)
In-Reply-To: <muwlfryvafsskt2l2hgv3szwzjfn7cswmmnoka6zlpz2bxj6lh@ugceww4kv3jr>

Hi Kent, hi.

Kent Overstreet - 15.03.24, 05:41:09 CET:
> there's a bug in 6.7 with filesystems that are mid upgrade and then get
> downgraded not getting marked in the superblock as downgraded, and this
> translates to a really horrific bug in splitbrain detection when the old
> version isn't updating member sequence nmubers and you go back to the
> new version - this results in every device being kicked out of the fs.

I take it that single device BCacheFS filesystems can be upgraded just fine?

I can also recreate and repopulate once I upgraded to 6.8. Still waiting a 
bit.

Best.
-- 
Martin



  reply	other threads:[~2024-03-15  9:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  4:41 bcachefs: do not run 6.7: upgrade to 6.8 immediately if you have a multi device fs Kent Overstreet
2024-03-15  8:57 ` Martin Steigerwald [this message]
2024-03-15 17:57   ` Kent Overstreet
2024-03-16 16:18     ` Martin Steigerwald
2024-03-16 16:41       ` Kent Overstreet
2024-03-16 16:49         ` Martin Steigerwald
2024-03-16 17:31           ` Martin Steigerwald
2024-03-16 18:08             ` Kent Overstreet

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=12416320.O9o76ZdvQC@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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