From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH zfsonlinux 0/2] update to 2.1.12
Date: Tue, 13 Jun 2023 11:57:51 +0200 [thread overview]
Message-ID: <20230613095753.514016-1-s.ivanov@proxmox.com> (raw)
ZFS 2.1.12 got released one week ago [0].
Some commits fix data-corruption with mmap on rollback or clone.
The issue with mountpoint=legacy mounts for rpool in Proxmox VE were
addressed by reverting the change that introduced it [1].
Potential performance-optimization in [2,3,4]
Improved handling of drive replacements [5] and draid-resilvering [6]
The additional patch pulled from debian upstream is small enough and seems
sensible
did some very superficial tests (migrate a container with replicaton
config forth and back and running ztest for 20 minutes), on 2 VMs upgraded
to bookworm.
Stoiko Ivanov (2):
update zfs submodule to 2.1.12
/lib/zfs-linux/trim: don't exit 1 if last pool isn't nvme-only
(Closes: #1030316)
[0] https://github.com/openzfs/zfs/releases/tag/zfs-2.1.12
[1] https://github.com/openzfs/zfs/pull/14908
[2] https://github.com/openzfs/zfs/pull/14493
[3] https://github.com/openzfs/zfs/pull/12790
[4] https://github.com/openzfs/zfs/pull/14428
[5] https://github.com/openzfs/zfs/pull/14861
[6] https://github.com/openzfs/zfs/pull/14892
debian/tree/zfsutils-linux/usr/lib/zfs-linux/trim | 2 +-
upstream | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2023-06-13 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 9:57 Stoiko Ivanov [this message]
2023-06-13 9:57 ` [pve-devel] [PATCH zfsonlinux 1/2] update zfs submodule " Stoiko Ivanov
2023-06-13 9:57 ` [pve-devel] [PATCH zfsonlinux 2/2] /lib/zfs-linux/trim: don't exit 1 if last pool isn't nvme-only (Closes: #1030316) Stoiko Ivanov
2023-06-13 14:48 ` [pve-devel] applied-series: [PATCH zfsonlinux 0/2] update to 2.1.12 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=20230613095753.514016-1-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--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