From: Marco Gaiarin <gaio@lilliput.linux.it>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] ZFS Upgrade...
Date: Wed, 24 Sep 2025 18:18:01 +0200 [thread overview]
Message-ID: <aNQZucwlcpq0wdlu@sv.lnf.it> (raw)
In-Reply-To: <58420306b884238ed47ae0a5b2c69913bd131ebb@antreich.com>
Mandi! Alwin Antreich
In chel di` si favelave...
> Did you look into the man page? `man zpool-features`
> You can find a list of features compatible with the grub version installed, see
> /usr/share/zfs/compatibility.d/
This is exactly one point: PVE8 have GRUB 2.06, so i think i've ro read
/usr/share/zfs/compatibility.d/grub2-2.06 that state:
# 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.
#
allocation_classes
async_destroy
block_cloning
device_rebuild
embedded_data
empty_bpobj
enabled_txg
hole_birth
log_spacemap
lz4_compress
resilver_defer
spacemap_histogram
spacemap_v2
zpool_checkpoint
so seems to me that this file list 'compatible feature', and i've to double
check it against the FS 'active' feature, so:
root@svpve3:~# zpool get all rpool-backup | grep feature@ | grep active | tr -s ' ' | cut -d ' ' -f 2 | cut -d '@' -f 2 | sort
embedded_data
empty_bpobj
enabled_txg
extensible_dataset
head_errlog
hole_birth
large_blocks
log_spacemap
lz4_compress
project_quota
spacemap_histogram
spacemap_v2
userobj_accounting
vdev_zaps_v2
zilsaxattr
but if i check a non-upgraded pool:
root@svpve3:~# zpool get all rpool | grep feature@ | grep active | tr -s ' ' | cut -d ' ' -f 2 | cut -d '@' -f 2 | sort
embedded_data
empty_bpobj
enabled_txg
extensible_dataset
hole_birth
log_spacemap
lz4_compress
project_quota
spacemap_histogram
spacemap_v2
userobj_accounting
And seems to me that also on a compatible pool there's still no match;
manapage also mention 'Read-only compatibility' (that suffices on boot), and
so i probably need to check every feature with dependencies and read
compatibility.
Really i don't understand... and my initial impression is that this note on
PVE docs is an autdated one, a leftover... but clearly i don't want to make
a server unbootable to make it a try. ;-)
> If your system is running in EFI mode already, then consider converting to
> systemd-boot.
So, implicitly you confirm that it is GRUB that have some incompatibilities,
not GRUB in legacy mode... I've understood well?
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-24 16:20 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
2025-09-23 12:52 ` Alwin Antreich via pve-user
[not found] ` <58420306b884238ed47ae0a5b2c69913bd131ebb@antreich.com>
2025-09-24 16:18 ` Marco Gaiarin [this message]
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=aNQZucwlcpq0wdlu@sv.lnf.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