From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH zfsonlinux 0/2] update to ZFS 2.1.3
Date: Fri, 11 Mar 2022 13:55:07 +0100 [thread overview]
Message-ID: <20220311125509.259035-1-s.ivanov@proxmox.com> (raw)
updates the submodule to the recently release zfs-2.1.3
* changeset does not look too exciting (kernel-compatibility fixes, testsuite,
FreeBSD)
* the addition of the systemd timer+service for regular scrubbing is something
user-visible (but already present in upstream and our debian packages for a
while)
* the zvol_open lock inversion we cherry-picked is contained in the new tag
* zed default for mailing has changed upstream:
e56dffe4b5cd00df2d46b75a80d3d17c8fe70eec
* the changes to the other patches were due to some refactorings:
745a7f78da95d1969613cd55fcb33df1b46c1e66
tested with the latest 5.13 kernel on 2 VMs (running ztest)
Stoiko Ivanov (2):
update submodule and patches to ZFS 2.1.3
add zfs-scrub timers+services to zfsutils-linux
...META-and-DCH-consistency-in-autoconf.patch | 4 +-
debian/patches/0005-Enable-zed-emails.patch | 17 +-
...md-unit-for-importing-specific-pools.patch | 2 +-
.../0012-Fix-zvol_open-lock-inversion.patch | 212 ------------------
debian/patches/series | 1 -
debian/zfsutils-linux.install | 3 +
upstream | 2 +-
7 files changed, 11 insertions(+), 230 deletions(-)
delete mode 100644 debian/patches/0012-Fix-zvol_open-lock-inversion.patch
--
2.30.2
next reply other threads:[~2022-03-11 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 12:55 Stoiko Ivanov [this message]
2022-03-11 12:55 ` [pve-devel] [PATCH zfsonlinux 1/2] update submodule and patches " Stoiko Ivanov
2022-03-11 12:55 ` [pve-devel] [PATCH zfsonlinux 2/2] add zfs-scrub timers+services to zfsutils-linux Stoiko Ivanov
2022-03-11 15:37 ` [pve-devel] applied-series: [PATCH zfsonlinux 0/2] update to ZFS 2.1.3 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=20220311125509.259035-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