From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id B3582792DA for ; Tue, 4 May 2021 10:10:13 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B1ACF2494F for ; Tue, 4 May 2021 10:10:13 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 8E1D32490F for ; Tue, 4 May 2021 10:10:12 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 5311D42A30 for ; Tue, 4 May 2021 10:10:12 +0200 (CEST) From: Fabian Ebner To: pve-devel@lists.proxmox.com Date: Tue, 4 May 2021 10:09:54 +0200 Message-Id: <20210504081004.21898-1-f.ebner@proxmox.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.000 Adjusted score from AWL reputation of From: address 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: [pve-devel] [PATCH-SERIES zsync] fix #1669: allow prepending storage ID 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: , X-List-Received-Date: Tue, 04 May 2021 08:10:13 -0000 which makes it possible to use pve-zsync for guests with disks with the same name on different storages, i.e. storageA:vm-123-disk-0 storageB:vm-123-disk-0 Currently they would collide to target/vm-123-disk-0 When the new prepend-storage-id flag is specified, they will be synced to target/storageA/vm-123-disk-0$ target/storageB/vm-123-disk-0$ instead. The first four patches are cleanups/usage description fixes. The next five patches are preparations for the last patch, which is the one actually implementing the new feature. Fabian Ebner (10): whitespace fix copyright: update year usage: describe flag parameters correctly usage: fix type for maxsnap add target_dataset function add check_dataset_exists function add create_file_system function parse disks: don't include colon in storage name variable parse disks: also include storage ID information fix #1669: add prepend-storage-id flag pve-zsync | 118 ++++++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 89 insertions(+), 29 deletions(-) -- 2.20.1