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 752DD1FF15F for ; Mon, 26 Aug 2024 00:55:40 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 11CB48F8F; Mon, 26 Aug 2024 00:56:00 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 morty.keekles.org 6936D19E1D68 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bryanfields.net; s=909DCF92-EFE7-11EB-9235-648EB8AF1B81; t=1724626517; bh=SVOfaHQclEtjagOtGb0qhjAzTAl0ejA9bGSslMCefjA=; h=Message-ID:Date:MIME-Version:From:To; b=CkF8n5Ste/r3uCFo3Uj3AfsPFdHYKbBEGcQ6047Fg0+GLO7PaOeaE72Kq+JSnDtXo Mo5DoX4+Hv+CfXXgHzs1mfi7ryQUsozGIyrr0SZ2qquXKaku3MKLjMftiDCAXNQfDE XisFvXm0h3osiVJR9aTjoU4r2jRjVkdRVCPEXe1ARloCnY0U8IjaljV/LHue/BR3UL nP0ZDgtqtX5Nbl8IRjKYNbUi6BQ+GB7spJFgtqkMNOvFMDxQ2KG6Ufn+5Hzr2P+Wos ImjRo50/Si84crXRCnV0oiKzkaqEeA3mV0uPgKT6OkuNyz/PBqGdhX3oCBOPh2I+Mu hLBYWb6a6tQaA== X-Virus-Scanned: amavis at morty.keekles.org Message-ID: Date: Sun, 25 Aug 2024 18:55:16 -0400 MIME-Version: 1.0 User-Agent: Mutt/1.12.0 (2019-05-25) Content-Language: en-US From: Bryan Fields To: pve-user@lists.proxmox.com X-SPAM-LEVEL: Spam detection results: 0 AWL 0.103 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_MISSING 0.1 Missing DMARC policy RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [PVE-User] local zfs storage and migration with different pool names X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE user list Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" I've built a new hypervisor to add to my cluster of older hypervisors. As part of this, I decided to place the root pool as a mirror across two NVME disks and make the local ZFS a pool of 5 2 disk mirrors with NVME for special devices in a mirror. This of course means I have rpool for the 128g boot drive and then localStoragePool/data for the local ZFS storage. I ran into the issue of Proxmox not supporting this configuration [1] and then down the rabbit hole of why and how to solve it. Online migration works, but offline and replication doesn't. This is a big problem and I'm surprised there's no way to alias storage in storage.conf. That being what it is, and me being stuck with my old servers for some time I don't have many options. The current servers are 8 SAS devices in a raidz2 pool as rpool. Nothing fancy, no special devices, and it boots (MBR, not EFI as it's not supported). What I'd like to do is rebuild/upgrade these servers and since the pool must be named the same, I was thinking of having a small rpool of 64gb per disk and then the rest of the disk as localStoragePool. I know that they say you shouldn't have two pools on the same physical device, but the rpool doesn't do anything other than logging and /etc/pve database stuff. Has anyone else done this or solved this problem in another way? [1] https://forum.proxmox.com/threads/replication-with-different-target-storage-name.35458/ [2] https://bugzilla.proxmox.com/show_bug.cgi?id=2087 -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user