From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id F421B1FF0B3 for ; Wed, 11 Nov 2026 16:05:02 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id B90B22162B; Wed, 11 Nov 2026 16:05:02 +0100 (CET) Message-ID: <861386f3-a00b-4b62-92da-840afe32bb29@proxmox.com> Date: Wed, 11 Nov 2026 16:04:57 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Christian Ebner Subject: Re: [PATCH proxmox-backup 8/9] docs: add explanation regarding ``rebuild-chunk-markers`` option To: Shan Shaji , pbs-devel@lists.proxmox.com References: <20261019160359.20851-1-s.shaji@proxmox.com> <20261019160359.20851-9-s.shaji@proxmox.com> Content-Language: en-US, de-DE In-Reply-To: <20261019160359.20851-9-s.shaji@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794409498041 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.418 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: Z4X6PFQKLOTLXDCJ3H7GVMWXOKFX2DKA X-Message-ID-Hash: Z4X6PFQKLOTLXDCJ3H7GVMWXOKFX2DKA X-MailFrom: c.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: One comment in-line. On 10/19/26 6:04 PM, Shan Shaji wrote: > Signed-off-by: Shan Shaji > --- > docs/storage.rst | 7 +++++-- > 1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git a/docs/storage.rst b/docs/storage.rst > index 2c6ba0a85..811b5ff44 100644 > --- a/docs/storage.rst > +++ b/docs/storage.rst > @@ -312,8 +312,11 @@ To setup a new datastore called ``my-s3-store`` placed in a bucket called ``pbs- > A datastore cannot be shared between multiple Proxmox Backup Server instances, only one instance can > operate on the datastore at a time. However, datastore contents used on an instance which is no > longer available can be reused on a fresh installation. To recreate the datastore, you must pass the > -``reuse-datastore`` and ``overwrite-in-use`` flags. Since the datastore name is used as prefix, the > -same datastore name must be used. comment: this deleted the important requirement that the same datastore name must be used. > +``reuse-datastore`` and ``overwrite-in-use`` flags. The optional ``rebuild-chunk-markers`` flag, > +disabled by default, creates local zero-byte chunk markers when reusing an S3 datastore. These markers > +allow Proxmox Backup Server to identify chunks already stored in S3 when they are not present in > +the in-memory cache, avoiding unnecessary uploads. The time required to create these markers depends > +on the number of chunks. > > .. code-block:: console >