public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs 1/2] pvesr: fix possible issues storage ID
Date: Fri, 29 Nov 2024 16:18:54 +0100	[thread overview]
Message-ID: <98851376-66b5-4aaa-9cff-1709e6274d77@proxmox.com> (raw)
In-Reply-To: <20241105110801.151806-1-a.lauterer@proxmox.com>

Am 05.11.24 um 12:08 schrieb Aaron Lauterer:
> The same storage needs to be configured on the target node for the
> replication to work.
> 
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
>  pvesr.adoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/pvesr.adoc b/pvesr.adoc
> index 9eda008..4fc2de1 100644
> --- a/pvesr.adoc
> +++ b/pvesr.adoc
> @@ -101,7 +101,7 @@ setup there may be another cause.
>  
>  * No free space left on the replication target storage.
>  
> -* Storage with same storage ID available on the target node
> +* Storage with same storage ID is not available on the target node
>  
>  NOTE: You can always use the replication log to find out what is causing the problem.
>  

Thanks! Did a small followup (add "the" for "the same storage ID") and
finish with a dot for consistency.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      parent reply	other threads:[~2024-11-29 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 11:08 [pve-devel] " Aaron Lauterer
2024-11-05 11:08 ` [pve-devel] [PATCH docs 2/2] pvesr: mention how to configure specific network for replication Aaron Lauterer
2024-11-29 15:17   ` Fiona Ebner
2024-12-04 16:08     ` Aaron Lauterer
2024-11-29 15:18 ` Fiona Ebner [this message]

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=98851376-66b5-4aaa-9cff-1709e6274d77@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=a.lauterer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal