public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
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-series: [PATCH zfsonlinux 0/3] update to 2.1.1
Date: Tue, 28 Sep 2021 07:13:22 +0200	[thread overview]
Message-ID: <4c33d8a4-9e90-e532-c57b-4339da056653@proxmox.com> (raw)
In-Reply-To: <20210927180706.3090234-1-s.ivanov@proxmox.com>

On 27.09.21 20:07, Stoiko Ivanov wrote:
> Changes from the RFC sent 20 days ago:
> * ZFS 2.1.1 was tagged upstream
> * the abi-tracking changes were ported to 2.1-release, rendering the ported
>   patches superfluous
> 
> Tested with the upcoming 5.13 kernel on 2 VMs with storage-replication:
> * created a snapshot before the upgrade on one machine,
> * upgraded both nodes
> * rebooted
> * migrated container
> * rolled back to the snapshot
> 
> all working as expected
> 

> 
> Stoiko Ivanov (3):
>   update submodule and patches to ZFS 2.1.1-staging
>   buildsys: adapt install paths for zfs 2.1.1
>   bump libzpool soname
> 
>  Makefile                                      |  2 +-
>  debian/control                                |  8 +--
>  ...ibzpool4linux.docs => libzpool5linux.docs} |  0
>  ...x.install.in => libzpool5linux.install.in} |  0
>  ...rides => libzpool5linux.lintian-overrides} |  0
>  ...ith-d-dev-disk-by-id-in-scan-service.patch |  6 +-
>  .../0006-dont-symlink-zed-scripts.patch       |  5 +-
>  .../patches/0007-Use-installed-python3.patch  |  4 +-
>  ...-move-manpage-arcstat-1-to-arcstat-8.patch | 61 +++++++++----------
>  debian/zfsutils-linux.install                 | 14 +++--
>  upstream                                      |  2 +-
>  11 files changed, 53 insertions(+), 49 deletions(-)
>  rename debian/{libzpool4linux.docs => libzpool5linux.docs} (100%)
>  rename debian/{libzpool4linux.install.in => libzpool5linux.install.in} (100%)
>  rename debian/{libzpool4linux.lintian-overrides => libzpool5linux.lintian-overrides} (100%)
> 



applied, thanks!




      parent reply	other threads:[~2021-09-28  5:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 18:07 [pve-devel] " Stoiko Ivanov
2021-09-27 18:07 ` [pve-devel] [PATCH zfsonlinux 1/3] update submodule and patches to ZFS 2.1.1-staging Stoiko Ivanov
2021-09-27 18:07 ` [pve-devel] [PATCH zfsonlinux 2/3] buildsys: adapt install paths for zfs 2.1.1 Stoiko Ivanov
2021-09-27 18:07 ` [pve-devel] [PATCH zfsonlinux 3/3] bump libzpool soname Stoiko Ivanov
2021-09-28  5:13 ` 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=4c33d8a4-9e90-e532-c57b-4339da056653@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal