all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 1/1] backup: Fix wrong unit for bandwidth limit
Date: Wed, 29 Mar 2023 14:34:32 +0200	[thread overview]
Message-ID: <20230329123436.2090248-2-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20230329123436.2090248-1-s.hanreich@proxmox.com>

The correct unit for the bwlimit is actually Kibibyte per second
rather than Kibibit per second.

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
 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 <integer>` 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




  reply	other threads:[~2023-03-29 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 12:34 [pve-devel] [PATCH-SERIES storage/docs/guest-common/qemu-server/common] Improve and unify documentation of bwlimit parameter Stefan Hanreich
2023-03-29 12:34 ` Stefan Hanreich [this message]
2023-03-29 12:34 ` [pve-devel] [PATCH pve-common 1/1] json schema: improve description " Stefan Hanreich
2023-03-29 12:34 ` [pve-devel] [PATCH qemu-server 1/1] qmrestore: " Stefan Hanreich
2023-03-29 12:34 ` [pve-devel] [PATCH pve-storage 1/1] volume export: explicitly state unit of bandwidth limit Stefan Hanreich
2023-03-29 12:34 ` [pve-devel] [PATCH pve-guest-common 1/1] vzdump: improve description of bwlimit parameter Stefan Hanreich
2023-06-06 15:57 ` [pve-devel] applied-series: [PATCH-SERIES storage/docs/guest-common/qemu-server/common] Improve and unify documentation " Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230329123436.2090248-2-s.hanreich@proxmox.com \
    --to=s.hanreich@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal