From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH zfsonlinux 0/2] update to 2.2.2
Date: Mon, 4 Dec 2023 12:27:50 +0100 [thread overview]
Message-ID: <20231204112752.976026-1-s.ivanov@proxmox.com> (raw)
Since ZFS 2.2.2 was released last week - and for now there were not
regressions noticed with it - updating to 2.2.2 should help
everyone to see that our version is not affected by the `dnode_is_dirty`
issue anymore.
The second patch was already present in my tests for 2.2.1:
https://lists.proxmox.com/pipermail/pve-devel/2023-November/060751.html
minimally tested on 2 VMs, with a few containers and storage-replication
configured.
Stoiko Ivanov (2):
update zfs submodule to 2.2.2 and refresh patches
d/zfsutils-linux.install: add zfs_prepare_disk and manpage
...-move-manpage-arcstat-1-to-arcstat-8.patch | 2 +-
...-guard-access-to-l2arc-MFU-MRU-stats.patch | 2 +-
...uncate_shares-without-etc-exports.d.patch} | 0
...ol-Remove-broken-blk-mq-optimization.patch | 99 ---------
...evert-zvol-Temporally-disable-blk-mq.patch | 123 -----------
...ten-bounds-for-noalloc-stat-availab.patch} | 0
...und-UBSAN-errors-for-variable-arrays.patch | 72 -------
...g-between-unencrypted-and-encrypted-.patch | 44 ----
...Add-a-tunable-to-disable-BRT-support.patch | 201 ------------------
...2.1-Disable-block-cloning-by-default.patch | 42 ----
...heck-dnode-and-its-data-for-dirtines.patch | 97 ---------
debian/patches/series | 11 +-
debian/zfsutils-linux.install | 2 +
upstream | 2 +-
14 files changed, 7 insertions(+), 690 deletions(-)
rename debian/patches/{0012-Fix-nfs_truncate_shares-without-etc-exports.d.patch => 0010-Fix-nfs_truncate_shares-without-etc-exports.d.patch} (100%)
delete mode 100644 debian/patches/0010-zvol-Remove-broken-blk-mq-optimization.patch
delete mode 100644 debian/patches/0011-Revert-zvol-Temporally-disable-blk-mq.patch
rename debian/patches/{0014-zpool-status-tighten-bounds-for-noalloc-stat-availab.patch => 0011-zpool-status-tighten-bounds-for-noalloc-stat-availab.patch} (100%)
delete mode 100644 debian/patches/0013-Workaround-UBSAN-errors-for-variable-arrays.patch
delete mode 100644 debian/patches/0015-Fix-block-cloning-between-unencrypted-and-encrypted-.patch
delete mode 100644 debian/patches/0016-Add-a-tunable-to-disable-BRT-support.patch
delete mode 100644 debian/patches/0017-zfs-2.2.1-Disable-block-cloning-by-default.patch
delete mode 100644 debian/patches/0018-dnode_is_dirty-check-dnode-and-its-data-for-dirtines.patch
--
2.39.2
next reply other threads:[~2023-12-04 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 11:27 Stoiko Ivanov [this message]
2023-12-04 11:27 ` [pve-devel] [PATCH zfsonlinux 1/2] update zfs submodule to 2.2.2 and refresh patches Stoiko Ivanov
2023-12-04 11:27 ` [pve-devel] [PATCH zfsonlinux 2/2] d/zfsutils-linux.install: add zfs_prepare_disk and manpage Stoiko Ivanov
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=20231204112752.976026-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 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.