From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 2/3] backup: Fix typos and grammar
Date: Tue, 21 Jul 2020 11:54:36 +0200 [thread overview]
Message-ID: <20200721095437.10316-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20200721095437.10316-1-a.lauterer@proxmox.com>
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
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
next prev parent reply other threads:[~2020-07-21 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 9:54 [pbs-devel] [PATCH proxmox-backup 1/3] docs: fix #2851 Add note about GC grace period Aaron Lauterer
2020-07-21 9:54 ` Aaron Lauterer [this message]
2020-07-21 9:54 ` [pbs-devel] [PATCH proxmox-backup 3/3] chunk_store: Fix typo in bail message Aaron Lauterer
2020-07-21 11:01 ` [pbs-devel] applied-series: [PATCH proxmox-backup 1/3] docs: fix #2851 Add note about GC grace period 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=20200721095437.10316-2-a.lauterer@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pbs-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