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 F170B1FF2D4 for ; Tue, 16 Jul 2024 16:09:14 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4D2231D090; Tue, 16 Jul 2024 16:09:43 +0200 (CEST) Date: Tue, 16 Jul 2024 16:09:39 +0200 From: Gabriel Goller To: Proxmox Backup Server development discussion Message-ID: <20240716140939.ts4oopzoor6d7gr6@luna.proxmox.com> References: <20240715101602.274244-1-c.ebner@proxmox.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240715101602.274244-1-c.ebner@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL -0.201 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 POISEN_SPAM_PILL 0.1 Meta: its spam POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pbs-devel] [RFC proxmox-backup 00/24] fix #3044: push datastore to remote X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Backup Server development discussion Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" Just a high level overview: - In the frontend, there is no way to see the difference between a push/pull sync job when the datastore names are the same. I think it's better if we add a second table for the push jobs (on the same page, something like in the "Prune & GC Jobs" tab.) - Sometimes a group fails to sync, I get an "sync group 'vm/114' failed pipelined request failed: no such chunk bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8". It seems like some chunks get added to the fixed index but haven't been uploaded yet. (Because sometimes, I also get this error on the receiving end: "POST /fixed_chunk: 400 Bad Request: backup already marked as finished.".) _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel