From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 7F9111FF163 for ; Thu, 19 Dec 2024 09:56:46 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B8B4C2E2ED; Thu, 19 Dec 2024 09:56:44 +0100 (CET) Message-ID: <4907685d-5331-40b1-8630-6ed71b9ff71e@proxmox.com> Date: Thu, 19 Dec 2024 09:56:37 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Proxmox VE development discussion , "d.kral@proxmox.com" References: <20241217154814.82121-1-f.ebner@proxmox.com> <20241217154814.82121-6-f.ebner@proxmox.com> <06d3843b-2e72-4394-ad79-a174195f7301@proxmox.com> <75eb7496-2e1c-4418-924d-74ac006fa6df@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: X-SPAM-LEVEL: Spam detection results: 0 AWL -0.052 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 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 Subject: Re: [pve-devel] [PATCH v2 storage 05/10] rbd plugin: implement volume import/export 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" Am 18.12.24 um 16:33 schrieb DERUMIER, Alexandre via pve-devel: >>> Am 18.12.24 um 15:20 schrieb Daniel Kral: >>>> - When exporting with "pvesm export ...", the volume has the same >> checksum as with "rbd export ..." with the size header prepended > >>> Well, I totally missed the existence of "rbd export" in my hurry to >>> get >>> this working. Seems to be about 1.5 times faster than mapping+dd from >>> some initial testing. Will use that in v3. > > Hi, fiona, rbd export|import, this is the way, like zfs send|receive. > (with snapshot support too, with export-diff|import-diff) > Saw that in the man page, and yes, would be the way to go for an 'rbd' transport format with incremental support similar to 'zfs' :) > I't really fast because, if I remember, it's use big block size and is > able to do parallelism. (can be tunned with --rbd-concurrent- > management-ops ) > We'll need to evaluate trade-off between speed and putting more load on the system/Ceph. After all, the disk move might not be the most important thing happening at that moment. > No related, but could it be possible to implement it, for simple > vm/template full cloning with source+target are both rbd ? It's really > faster with 'qemu-img convert' Hmm, we could shift offline copy of images to the storage layer (at least in some cases). We just need a version of storage_migrate() that goes to the local node instead of SSH to a different one. Could you please open a feature request for this? _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel