From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id C85AA1FF2CF for ; Thu, 11 Jul 2024 14:00:05 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B751032CA9; Thu, 11 Jul 2024 14:00:28 +0200 (CEST) Date: Thu, 11 Jul 2024 14:00:25 +0200 From: Christoph Heiss To: Proxmox VE development discussion Message-ID: <66ybsndl3vxnhf6qf5ipp66o2sh6bpusrkbdierjagpem3lhsb@ymvos363toni> References: <20240516102837.422278-1-c.heiss@proxmox.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240516102837.422278-1-c.heiss@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.017 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH installer 0/3] add check/rename for already-existing ZFS rpool X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" v3 (already) out: https://lists.proxmox.com/pipermail/pve-devel/2024-July/064635.html On Thu, May 16, 2024 at 12:28:32PM GMT, Christoph Heiss wrote: > Pretty straight forward overall, implements a check for an exising > `rpool` on the system and ask the user whether they would like to rename > it, much in the same way as it works for VGs already. > > Without this, the installer would silently create a second (and thus > conflicting) `rpool` and cause a boot failure after the installation, > since it does not know which pool to import exactly. > > Christoph Heiss (3): > proxmox: add zfs module for retrieving importable zpool info > low-level: install: split out random disk uid generation > low-level: install: check for already-existing `rpool` on install > > Proxmox/Install.pm | 47 ++++++++++++++++++++++++++++++++----- > Proxmox/Makefile | 1 + > Proxmox/Sys/ZFS.pm | 43 ++++++++++++++++++++++++++++++++++ > test/Makefile | 6 +++++ > test/zfs-get-pool-list.pl | 49 +++++++++++++++++++++++++++++++++++++++ > 5 files changed, 140 insertions(+), 6 deletions(-) > create mode 100644 Proxmox/Sys/ZFS.pm > create mode 100755 test/zfs-get-pool-list.pl > > -- > 2.44.0 > > > > _______________________________________________ > pve-devel mailing list > pve-devel@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > > _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel