From: Martin Steigerwald <martin@lichtvoll.de>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org
Subject: Re: Questions related to BCacheFS
Date: Mon, 20 Nov 2023 18:34:33 +0100 [thread overview]
Message-ID: <3539807.iIbC2pHGDl@lichtvoll.de> (raw)
In-Reply-To: <20231119231001.tb3teva5j4azqp7i@moria.home.lan>
Kent Overstreet - 20.11.23, 00:10:01 CET:
> Maybe I need to continue testing BCacheFS on a virtual machine, but I'd
>
> > really love to have a BCacheFS filesystem on my laptop and actually
> > really using it for something. Well I am going to leave it at that
> > and probably research on this after the weekend. Now it is time to
> > have a Sunday off.
> The Nixos install process with bcachefs as root is pretty smooth, just
> make sure to set up a separate filesystem for /boot!
Thanks for that idea.
While it might have been that those BTRFS filesystems that got corrupted
where corrupted by an "thou shalt not resume from this hibernation image"
I will indeed wait before I try 5.7 kernel again on this laptop. Also I
will likely wait for an update bcachefs-tools package. I still don't know
why GRUB greeted me with a command prompt after having removed 5.7 kernel
again. My current idea on why the BTRFS corruption happened is cause of
kernel 6.6.1 resuming from hibernation after I fixed up the boot loader in
two GRML sessions, accessing / and /boot, but not doing anything to
invalidate the hibernation image on the swap volume. Reminder to self:
Absolutely do that next time!
I had to restore / and /home BTRFS filesystem as well as /boot, which got
GRUB broken once more:
xfsprogs-6.5.0 with grub 2.12~rc1-12: unknown filesystem
https://lore.kernel.org/linux-xfs/1889442.tdWV9SEqCh@lichtvoll.de/T/#t
So yes I am very well aware of the advantages of a separate /boot. But
even with that GRUB was funny on me. Maybe that is why I have seen Ext4 in
Ext3 mode for /boot. It does not gain new features.
I may investigate an alternative boot loader… it is not the first time GRUB
broke on new filesystem features and it is not even surprising. It would be
best to have GRUB use a very simple file system that does not gain new
features. A bootfs filesystem just for the purposes of a boot loader to
store a few files and be done with it.
Anyway, it will be a VM for now.
Ciao,
--
Martin
next prev parent reply other threads:[~2023-11-20 17:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 19:15 Questions related to BCacheFS Martin Steigerwald
2023-11-18 19:50 ` Kent Overstreet
2023-11-18 20:57 ` Martin Steigerwald
2023-11-18 21:07 ` Kent Overstreet
2023-11-18 23:15 ` Martin Steigerwald
2023-11-18 23:42 ` Kent Overstreet
2023-11-19 11:13 ` Martin Steigerwald
2023-11-19 16:43 ` Martin Steigerwald
2023-11-19 23:10 ` Kent Overstreet
2023-11-20 17:34 ` Martin Steigerwald [this message]
2023-12-03 16:58 ` Martin Steigerwald
2023-12-18 16:50 ` Martin Steigerwald
2023-12-28 22:29 ` deletion time of big files (was: Re: Questions related to BCacheFS) Martin Steigerwald
2023-12-29 18:48 ` Kent Overstreet
2023-12-30 10:51 ` Martin Steigerwald
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=3539807.iIbC2pHGDl@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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