From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH zfsonlinux 0/2] update ZFS to 2.2.6
Date: Thu, 5 Sep 2024 14:24:30 +0200 [thread overview]
Message-ID: <4ef7e38d-c945-4143-8289-d9759c10a402@proxmox.com> (raw)
In-Reply-To: <20240905094429.956503-1-s.ivanov@proxmox.com>
Am 05/09/2024 um 11:44 schrieb Stoiko Ivanov:
> This patchset updates ZFS to 2.2.6, which was released last night.
> It supersedes the update to 2.2.5:
> https://lore.proxmox.com/pve-devel/20240820164512.1532793-1-s.ivanov@proxmox.com/
>
> The usrmerge part of the above series will be resent independently later,
> as we probably don't want to do that in between releases (as talked
> off-list with Thomas).
>
> In addition to the changes from 2.2.5, 2.2.6 contains a fixes discard on
> zvols, that might affect kernel 6.8:
> https://github.com/openzfs/zfs/pull/16462
> https://github.com/openzfs/zfs/pull/16454
>
> additionally it contains a few relevant fixes for more recent kernels
> (6.10+)
>
> It also pulls in a fix for bash-completion that was reported in our
> bugzilla: https://bugzilla.proxmox.com/show_bug.cgi?id=5565
>
> Tested minimally on a pair of VMs (migrate a container, storage
> replication).
>
> Relevant part of the cover-letter for the superseded series for ZFS-2.2.5:
> This patchset updates ZFS to 2.2.5 which was released two weeks ago [0]
> The changes don't look too scary, but could prevent a few issues in not so
> common use-cases for us e.g.:
> https://github.com/openzfs/zfs/pull/16359/commits/4d2f7f9839d12708417457cd57cf43d15cae5e92
> https://github.com/openzfs/zfs/pull/16359/commits/6f27c4cadd29eb9b850c1c66bf71ef9ba119b955
> https://github.com/openzfs/zfs/pull/16359/commits/ef08cb26dae6b3c2e930e66852f13329babb7c2e
>
> [0] https://github.com/openzfs/zfs/pull/16359
>
> Stoiko Ivanov (2):
> update zfs submodule to 2.2.6
> debian: remove libzfsbootenv1linux.install
>
> debian/libzfsbootenv1linux.install | 1 -
> upstream | 2 +-
> 2 files changed, 1 insertion(+), 2 deletions(-)
> delete mode 100644 debian/libzfsbootenv1linux.install
>
applied series, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-09-05 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 9:44 [pve-devel] " Stoiko Ivanov
2024-09-05 9:44 ` [pve-devel] [PATCH zfsonlinux 1/2] update zfs submodule " Stoiko Ivanov
2024-09-05 9:44 ` [pve-devel] [PATCH zfsonlinux 2/2] debian: remove libzfsbootenv1linux.install Stoiko Ivanov
2024-09-05 12:24 ` 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=4ef7e38d-c945-4143-8289-d9759c10a402@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.