From: Krzysztof Hajdamowicz <krzysztof@hajdamowicz.info>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] Use of ZFS 2.3.x in PVE 8.4
Date: Wed, 7 May 2025 17:27:09 +0200 [thread overview]
Message-ID: <CAG4rwVSvbXtcbxjA52EsWc=ei+L3bemT8jXoWX28T-rOmMVVaw@mail.gmail.com> (raw)
Hello,
A few months ago, I decided to experiment with bcachefs on my PVE 8.x home
server.
So far, the experience has been positive, although it requires building the
latest kernel from Linus's source tree, which can be a bit on the edge.
With some external assistance, I've managed to build the latest kernel
versions as a pve-kernel package [1], using the vanilla Linus repository
(latest git tag) with the latest bcachefs patches, and OpenZFS sources
directly from the upstream repository.
This setup means that the compatibility with OpenZFS 2.2.7 dictates the
pace at which I can compile new kernels.
Proxmox uses ZFS 2.2.7 in its kernel, which necessitates backporting
patches from the 2.3 branch [2].
My question is: To simplify my kernel flavor, which is focused on bcachefs,
can I migrate to the ZFS 2.3 branch, or does PVE rely on 2.2.7, making 2.3
potentially problematic?
For reference:
1: https://github.com/KrzysztofHajdamowicz/pve-kernel
2: https://github.com/openzfs/zfs/pull/17229#issuecomment-2857379669
Sincerely,
--
Krzysztof Hajdamowicz
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-05-07 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 15:27 Krzysztof Hajdamowicz [this message]
2025-05-14 18:32 ` Thomas Lamprecht
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='CAG4rwVSvbXtcbxjA52EsWc=ei+L3bemT8jXoWX28T-rOmMVVaw@mail.gmail.com' \
--to=krzysztof@hajdamowicz.info \
--cc=pve-devel@lists.proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal