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 18:31:58 +0100 [thread overview]
Message-ID: <12401121.O9o76ZdvQC@lichtvoll.de> (raw)
In-Reply-To: <1962788.PYKUYFuaPT@lichtvoll.de>
Martin Steigerwald - 16.03.24, 17:49:52 CET:
> > > Unfortunately I need to do exactly that, as 6.8.1 breaks hibernation
>
> > > on ThinkPad T14 AMD Gen 1:
> […]
>
> > run this tree then:
> >
> > https://evilpiepirate.org/git/bcachefs.git/log/?h=bcachefs-for-v6.7
>
> Wonderful. Thanks! Compiling this one instead. Shall I report something
> to you once I booted into it? I read you had difficulties getting those
> patches into stable.
It seems that the downgrade succeeded.
First mount:
[ 22.565053] bcachefs (dm-5): mounting version 1.4: (unknown version) opts=metadata_checksum=xxhash,data_checksum=xxhash,compression=lz4
[ 22.565686] bcachefs (dm-5): recovering from clean shutdown, journal seq 116996
[ 22.565717] bcachefs (dm-5): Version downgrade required:
[ 22.590487] bcachefs (dm-5): alloc_read... done
[ 22.597896] bcachefs (dm-5): stripes_read... done
[ 22.597930] bcachefs (dm-5): snapshots_read... done
[ 22.651106] bcachefs (dm-5): journal_replay... done
[ 22.651667] bcachefs (dm-5): resume_logged_ops... done
[ 22.651736] bcachefs (dm-5): going read-write
I wonder whether there was some text supposed to follow
"Version downgrade required:". The line feed was in the output.
Second mount:
[ 113.059224] bcachefs (dm-5): mounting version 1.3: rebalance_work opts=metadata_checksum=xxhash,data_checksum=xxhash,compression=lz4
[ 113.059259] bcachefs (dm-5): recovering from clean shutdown, journal seq 117013
[ 113.083911] bcachefs (dm-5): alloc_read... done
[ 113.091268] bcachefs (dm-5): stripes_read... done
[ 113.091281] bcachefs (dm-5): snapshots_read... done
[ 113.142374] bcachefs (dm-5): journal_replay... done
[ 113.142390] bcachefs (dm-5): resume_logged_ops... done
[ 113.142406] bcachefs (dm-5): going read-write
Thanks,
--
Martin
next prev parent reply other threads:[~2024-03-16 17:32 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
2024-03-16 16:41 ` Kent Overstreet
2024-03-16 16:49 ` Martin Steigerwald
2024-03-16 17:31 ` Martin Steigerwald [this message]
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=12401121.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