From: Martin Steigerwald <martin@lichtvoll.de>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: bcachefs: do not run 6.7: upgrade to 6.8 immediately if you have a multi device fs
Date: Sat, 16 Mar 2024 17:18:30 +0100 [thread overview]
Message-ID: <4555054.LvFx2qVVIh@lichtvoll.de> (raw)
In-Reply-To: <2c3smz5wnk5z2kaqyqbo6kr3bb6dtvanfvupsqdydggzmvkukc@xssb53m4lyey>
Kent Overstreet - 15.03.24, 18:57:51 CET:
> > 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.
>
> No need to recreate and repopulate - you just don't want to be going
> back to 6.7 from a newer version.
Unfortunately I need to do exactly that, as 6.8.1 breaks hibernation on
ThinkPad T14 AMD Gen 1:
[regression] 6.8.1: fails to hibernate with
pm_runtime_force_suspend+0x0/0x120 returns -16
https://lore.kernel.org/linux-pm/12401263.O9o76ZdvQC@lichtvoll.de/T/#t
No luck with kernel upgrades these days. :(
I will backup the test filesystem so in case something breaks I can
recreate and repopulate it again. Downgrading to 6.7.10 then and will see
what happens. Can repopulate from backup again if need be. Also when
upgrading to 6.8 again after the regression has been fixed.
Best,
--
Martin
next prev parent reply other threads:[~2024-03-16 16:18 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
2024-03-15 17:57 ` Kent Overstreet
2024-03-16 16:18 ` Martin Steigerwald [this message]
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=4555054.LvFx2qVVIh@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