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 73F7F64DB8 for ; Tue, 21 Jul 2020 11:54:39 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 71C0A16F7E for ; Tue, 21 Jul 2020 11:54:39 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS id 75D8316F74 for ; Tue, 21 Jul 2020 11:54:38 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 3ABDD432CD for ; Tue, 21 Jul 2020 11:54:38 +0200 (CEST) From: Aaron Lauterer To: pbs-devel@lists.proxmox.com Date: Tue, 21 Jul 2020 11:54:36 +0200 Message-Id: <20200721095437.10316-2-a.lauterer@proxmox.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20200721095437.10316-1-a.lauterer@proxmox.com> References: <20200721095437.10316-1-a.lauterer@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.000 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [backup.rs] Subject: [pbs-devel] [PATCH proxmox-backup 2/3] backup: Fix typos and grammar 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: , X-List-Received-Date: Tue, 21 Jul 2020 09:54:39 -0000 Signed-off-by: Aaron Lauterer --- src/backup.rs | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/src/backup.rs b/src/backup.rs index 10a65d6c..cb1426ab 100644 --- a/src/backup.rs +++ b/src/backup.rs @@ -40,21 +40,21 @@ //! //! Acquire shared lock for ChunkStore (process wide). //! -//! Note: When creating .idx files, we create temporary (.tmp) file, +//! Note: When creating .idx files, we create temporary a (.tmp) file, //! then do an atomic rename ... //! //! //! * Garbage Collect: //! //! Acquire exclusive lock for ChunkStore (process wide). If we have -//! already an shared lock for ChunkStore, try to updraged that +//! already a shared lock for the ChunkStore, try to upgrade that //! lock. //! //! //! * Server Restart //! -//! Try to abort running garbage collection to release exclusive -//! ChunkStore lock asap. Start new service with existing listening +//! Try to abort the running garbage collection to release exclusive +//! ChunkStore locks ASAP. Start the new service with the existing listening //! socket. //! //! @@ -62,10 +62,10 @@ //! //! Deleting backups is as easy as deleting the corresponding .idx //! files. Unfortunately, this does not free up any storage, because -//! those files just contains references to chunks. +//! those files just contain references to chunks. //! //! To free up some storage, we run a garbage collection process at -//! regular intervals. The collector uses an mark and sweep +//! regular intervals. The collector uses a mark and sweep //! approach. In the first phase, it scans all .idx files to mark used //! chunks. The second phase then removes all unmarked chunks from the //! store. @@ -90,12 +90,12 @@ //! amount of time ago (by default 24h). So we may only delete chunks //! with `atime` older than 24 hours. //! -//! Another problem arise from running backups. The mark phase does +//! Another problem arises from running backups. The mark phase does //! not find any chunks from those backups, because there is no .idx //! file for them (created after the backup). Chunks created or //! touched by those backups may have an `atime` as old as the start -//! time of those backup. Please not that the backup start time may -//! predate the GC start time. Se we may only delete chunk older than +//! time of those backups. Please note that the backup start time may +//! predate the GC start time. So we may only delete chunks older than //! the start time of those running backup jobs. //! //! -- 2.20.1