From: Marco Gaiarin <gaio@lilliput.linux.it>
To: Marco Gaiarin <gaio@lilliput.linux.it>
Cc: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] ZFS Upgrade...
Date: Mon, 22 Sep 2025 16:21:48 +0200 [thread overview]
Message-ID: <qk28ql-lrd2.ln1@leia.lilliput.linux.it> (raw)
In-Reply-To: <m27opl-jqc2.ln1@leia.lilliput.linux.it>; from SmartGate on Mon, Sep 22, 2025 at 22:36:01PM +0200
Someone have some feedback on this? Really i don't understand... Thanks.
> We have upgraded our server from PVE6 to PVE8, waited some month to be sure
> there's no incompatibilities and now we are ready to remove older kernels,
> and upgrade ZFS.
>
> Current situation is:
>
> root@svpve3:~# zfs upgrade
> This system is currently running ZFS filesystem version 5.
>
> All filesystems are formatted with the current version.
>
> and:
>
> root@svpve3:~# zpool upgrade
> This system supports ZFS pool feature flags.
>
> All pools are formatted using feature flags.
>
>
> Some supported features are not enabled on the following pools. Once a
> feature is enabled the pool may become incompatible with software
> that does not support the feature. See zpool-features(7) for details.
>
> Note that the pool 'compatibility' feature can be used to inhibit
> feature upgrades.
>
> POOL FEATURE
> ---------------
> rpool
> draid
> zilsaxattr
> head_errlog
> blake3
> block_cloning
> vdev_zaps_v2
> rpool-backup
> draid
> zilsaxattr
> head_errlog
> blake3
> block_cloning
> vdev_zaps_v2
>
> So, there's no zfs upgrade needed, but zpool is.
>
>
> First question: i've read:
> https://pve.proxmox.com/wiki/ZFS_on_Linux#sysadmin_zfs_features
> and on detail:
> A system with root on ZFS, that still boots using GRUB will become unbootable if a new feature is active on the rpool, due to the incompatible implementation of ZFS in GRUB.
>
> looking at 'zpool-features', GRUB 2.06 compatible features seems on file
> /usr/share/zfs/compatibility.d/grub2-2.06, that report:
>
> # Features which are supported by GRUB2 versions prior to v2.12.
> #
> # GRUB is not able to detect ZFS pool if snaphsot of top level boot pool
> # is created. This issue is observed with GRUB versions before v2.12 if
> # extensible_dataset feature is enabled on ZFS boot pool.
> #
> # This file lists all read-only comaptible features except
> # extensible_dataset and any other feature that depends on it.
>
> After upgrading the non-boot ZFS pool, i get this:
>
> root@svpve3:~# zpool get all rpool-backup | grep feature@ | grep enabled | sort
> rpool-backup feature@allocation_classes enabled local
> rpool-backup feature@async_destroy enabled local
> rpool-backup feature@blake3 enabled local
> rpool-backup feature@block_cloning enabled local
> rpool-backup feature@bookmarks enabled local
> rpool-backup feature@bookmark_v2 enabled local
> rpool-backup feature@bookmark_written enabled local
> rpool-backup feature@device_rebuild enabled local
> rpool-backup feature@device_removal enabled local
> rpool-backup feature@draid enabled local
> rpool-backup feature@edonr enabled local
> rpool-backup feature@enabled_txg active local
> rpool-backup feature@encryption enabled local
> rpool-backup feature@filesystem_limits enabled local
> rpool-backup feature@large_dnode enabled local
> rpool-backup feature@livelist enabled local
> rpool-backup feature@multi_vdev_crash_dump enabled local
> rpool-backup feature@obsolete_counts enabled local
> rpool-backup feature@redacted_datasets enabled local
> rpool-backup feature@redaction_bookmarks enabled local
> rpool-backup feature@resilver_defer enabled local
> rpool-backup feature@sha512 enabled local
> rpool-backup feature@skein enabled local
> rpool-backup feature@vdev_zaps_v2 enabled local
> rpool-backup feature@zilsaxattr enabled local
> rpool-backup feature@zpool_checkpoint enabled local
> rpool-backup feature@zstd_compress enabled local
>
> but it is unclear to me how to check compatibility issue: seems to there's
> no 'extensible_dataset' so i'm safe... or better, seems active BOTH on
> upgraded and non-upgraded dataset, and was not on feature list to be enabled
> by upgrade...
>
> root@svpve3:~# zpool get all rpool | grep feature@ | grep extensible_dataset
> rpool feature@extensible_dataset active local
>
> root@svpve3:~# zpool get all rpool-backup | grep feature@ | grep extensible_dataset
> rpool-backup feature@extensible_dataset active local
>
>
> There's some better description of these incompatibilities, or some
> reference ZFS or GRUB docs about this?
>
>
> Thanks.
>
--
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2025-09-22 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 13:59 Marco Gaiarin
2025-09-22 14:21 ` Marco Gaiarin [this message]
2025-09-23 12:52 ` Alwin Antreich via pve-user
[not found] ` <58420306b884238ed47ae0a5b2c69913bd131ebb@antreich.com>
2025-09-24 16:18 ` Marco Gaiarin
2025-09-27 15:32 ` Alwin Antreich via pve-user
2025-09-30 16:37 ` Marco Gaiarin
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=qk28ql-lrd2.ln1@leia.lilliput.linux.it \
--to=gaio@lilliput.linux.it \
--cc=pve-user@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