public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Krzysztof Hajdamowicz <krzysztof@hajdamowicz.info>
Subject: Re: [pve-devel] Use of ZFS 2.3.x in PVE 8.4
Date: Wed, 14 May 2025 20:32:06 +0200	[thread overview]
Message-ID: <6963a774-9081-4ff7-8ad8-b0d7f919c4fb@proxmox.com> (raw)
In-Reply-To: <CAG4rwVSvbXtcbxjA52EsWc=ei+L3bemT8jXoWX28T-rOmMVVaw@mail.gmail.com>

Hello,

Am 07.05.25 um 17:27 schrieb Krzysztof Hajdamowicz:
> 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.

Thanks for sharing your experience; bcachefs _is_ sounding interesting, but
due to it still being marked as experimental and some on-disk format changes
still being planned we did not bother in checking it out closer. Once it
stabilizes we definitively will evaluate it though.

> 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?

FWIW, you could also stop compiling ZFS completely if you do not use it
anyway, then you won't be limited by it's compatibility with upstream
Linux.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      reply	other threads:[~2025-05-14 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 15:27 Krzysztof Hajdamowicz
2025-05-14 18:32 ` Thomas Lamprecht [this message]

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=6963a774-9081-4ff7-8ad8-b0d7f919c4fb@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=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