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 29D0F9254A for ; Wed, 29 Mar 2023 14:34:39 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0AD463B201 for ; Wed, 29 Mar 2023 14:34:39 +0200 (CEST) Received: from lana.proxmox.com (unknown [94.136.29.99]) by firstgate.proxmox.com (Proxmox) with ESMTP for ; Wed, 29 Mar 2023 14:34:38 +0200 (CEST) Received: by lana.proxmox.com (Postfix, from userid 10043) id 533032C1F6A; Wed, 29 Mar 2023 14:34:38 +0200 (CEST) From: Stefan Hanreich To: pve-devel@lists.proxmox.com Date: Wed, 29 Mar 2023 14:34:32 +0200 Message-Id: <20230329123436.2090248-2-s.hanreich@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20230329123436.2090248-1-s.hanreich@proxmox.com> References: <20230329123436.2090248-1-s.hanreich@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.479 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 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Subject: [pve-devel] [PATCH pve-docs 1/1] backup: Fix wrong unit for bandwidth limit 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: Wed, 29 Mar 2023 12:34:39 -0000 The correct unit for the bwlimit is actually Kibibyte per second rather than Kibibit per second. Signed-off-by: Stefan Hanreich --- vzdump.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vzdump.adoc b/vzdump.adoc index ce46529..f3eadcd 100644 --- a/vzdump.adoc +++ b/vzdump.adoc @@ -398,7 +398,7 @@ limit. A bigger per-job limit will only overwrite the per-storage limit if you have `Data.Allocate' permissions on the affected storage. You can use the `--bwlimit ` option from the restore CLI commands -to set up a restore job specific bandwidth limit. Kibit/s is used as unit +to set up a restore job specific bandwidth limit. KiB/s is used as unit for the limit, this means passing `10240' will limit the read speed of the backup to 10 MiB/s, ensuring that the rest of the possible storage bandwidth is available for the already running virtual guests, and thus the backup -- 2.30.2