all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH proxmox-backup/proxmox-backup-restore-image] update and adapt to ZFS 2.3 and kernel 6.14
Date: Mon,  2 Jun 2025 11:47:50 +0200	[thread overview]
Message-ID: <20250602094756.519927-1-s.ivanov@proxmox.com> (raw)

While checking our codebase for potential uses of non-usr-merged paths
for ZFS I noticed the file-restore uses absolute paths for most commands.

As the daemon runs in an isolated environment we provide sticking to
absolute paths, instead of adding a PATH variable for Command::new to
search seems a sensible option.

Instead this patch creates a usr-merged environment in the initramfs,
to prevent issues occuring with changed paths in future packages.

During testing a change in `zpool import` was found, resulting in the patch
for proxmox-backup.

Additionally I looked through the kernel config options for newly added
filesystems to add.

Tested minimally with a backup of a VM containing a zpool.

proxmox-backup-restore-image:
Stoiko Ivanov (5):
  build initramfs: usr-merge initramfs
  update ZFS to 2.3.2
  build initramfs: remove additional ZFS scripts
  update ubuntu-kernel to Ubuntu-6.14.0-22.22
  kernel: enable more filesystem options

 src/build_initramfs.sh       | 10 ++++++++--
 src/config-base              | 10 +++++++++-
 src/submodules/ubuntu-kernel |  2 +-
 src/submodules/zfsonlinux    |  2 +-
 4 files changed, 19 insertions(+), 5 deletions(-)

proxmox-backup:
Stoiko Ivanov (1):
  restore-daemon: adapt to zpool output changes in 2.3

 proxmox-restore-daemon/src/proxmox_restore_daemon/disk.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


WARNING: multiple messages have this Message-ID
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup/proxmox-backup-restore-image] update and adapt to ZFS 2.3 and kernel 6.14
Date: Mon,  2 Jun 2025 11:47:50 +0200	[thread overview]
Message-ID: <20250602094756.519927-1-s.ivanov@proxmox.com> (raw)

While checking our codebase for potential uses of non-usr-merged paths
for ZFS I noticed the file-restore uses absolute paths for most commands.

As the daemon runs in an isolated environment we provide sticking to
absolute paths, instead of adding a PATH variable for Command::new to
search seems a sensible option.

Instead this patch creates a usr-merged environment in the initramfs,
to prevent issues occuring with changed paths in future packages.

During testing a change in `zpool import` was found, resulting in the patch
for proxmox-backup.

Additionally I looked through the kernel config options for newly added
filesystems to add.

Tested minimally with a backup of a VM containing a zpool.

proxmox-backup-restore-image:
Stoiko Ivanov (5):
  build initramfs: usr-merge initramfs
  update ZFS to 2.3.2
  build initramfs: remove additional ZFS scripts
  update ubuntu-kernel to Ubuntu-6.14.0-22.22
  kernel: enable more filesystem options

 src/build_initramfs.sh       | 10 ++++++++--
 src/config-base              | 10 +++++++++-
 src/submodules/ubuntu-kernel |  2 +-
 src/submodules/zfsonlinux    |  2 +-
 4 files changed, 19 insertions(+), 5 deletions(-)

proxmox-backup:
Stoiko Ivanov (1):
  restore-daemon: adapt to zpool output changes in 2.3

 proxmox-restore-daemon/src/proxmox_restore_daemon/disk.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.39.5



_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


             reply	other threads:[~2025-06-02  9:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02  9:47 Stoiko Ivanov [this message]
2025-06-02  9:47 ` [pbs-devel] " Stoiko Ivanov
2025-06-02  9:47 ` [pve-devel] [PATCH proxmox-backup-restore-image 1/5] build initramfs: usr-merge initramfs Stoiko Ivanov
2025-06-02  9:47   ` [pbs-devel] " Stoiko Ivanov
2025-06-02  9:47 ` [pbs-devel] [PATCH proxmox-backup-restore-image 2/5] update ZFS to 2.3.2 Stoiko Ivanov
2025-06-02  9:47   ` [pve-devel] " Stoiko Ivanov
2025-06-02  9:47 ` [pve-devel] [PATCH proxmox-backup-restore-image 3/5] build initramfs: remove additional ZFS scripts Stoiko Ivanov
2025-06-02  9:47   ` [pbs-devel] " Stoiko Ivanov
2025-06-02  9:47 ` [pve-devel] [PATCH proxmox-backup-restore-image 4/5] update ubuntu-kernel to Ubuntu-6.14.0-22.22 Stoiko Ivanov
2025-06-02  9:47   ` [pbs-devel] " Stoiko Ivanov
2025-06-02  9:47 ` [pbs-devel] [PATCH proxmox-backup-restore-image 5/5] kernel: enable more filesystem options Stoiko Ivanov
2025-06-02  9:47   ` [pve-devel] " Stoiko Ivanov
2025-06-02  9:47 ` [pbs-devel] [PATCH proxmox-backup 1/1] restore-daemon: adapt to zpool output changes in 2.3 Stoiko Ivanov
2025-06-02  9:47   ` [pve-devel] " Stoiko Ivanov
2025-06-03  8:59 ` [pbs-devel] applied: [PATCH proxmox-backup/proxmox-backup-restore-image] update and adapt to ZFS 2.3 and kernel 6.14 Fabian Grünbichler
2025-06-03  8:59   ` [pve-devel] applied: [pbs-devel] " Fabian Grünbichler

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=20250602094756.519927-1-s.ivanov@proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=pbs-devel@lists.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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal