From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
by lore.proxmox.com (Postfix) with ESMTPS id C46C01FF161
for <inbox@lore.proxmox.com>; Tue, 13 Aug 2024 12:24:12 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id CBF113F36E;
Tue, 13 Aug 2024 12:24:27 +0200 (CEST)
From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Date: Tue, 13 Aug 2024 12:23:04 +0200
Message-Id: <20240813102305.6-1-a.zeidler@proxmox.com>
MIME-Version: 1.0
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.083 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
RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
T_SCC_BODY_TEXT_LINE -0.01 -
Subject: [pve-devel] [PATCH docs] local-zfs: correct language errors
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
---
local-zfs.adoc | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/local-zfs.adoc b/local-zfs.adoc
index 130f9d6..7ddf50a 100644
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -442,7 +442,7 @@ recommend to:
# zpool create -f -o ashift=12 <pool> <device> log <log-device>
----
-In above example a single `<device>` and a single `<log-device>` is used, but you
+In the example above, a single `<device>` and a single `<log-device>` is used, but you
can also combine this with other RAID variants, as described in the
xref:sysadmin_zfs_create_new_zpool_raid0[Create a new pool with RAID] section.
@@ -465,19 +465,19 @@ protection that you want to use for improving the overall performance of your
pool.
As the maximum size of a log device should be about half the size of the
-installed physical memory, it means that the ZIL will mostly likely only take up
+installed physical memory, it means that the ZIL will most likely only take up
a relatively small part of the SSD, the remaining space can be used as cache.
First you have to create two GPT partitions on the SSD with `parted` or `gdisk`.
-Then you're ready to add them to an pool:
+Then you're ready to add them to a pool:
.Add both, a separate log device and a second-level cache, to an existing pool
----
# zpool add -f <pool> log <device-part1> cache <device-part2>
----
-Just replay `<pool>`, `<device-part1>` and `<device-part2>` with the pool name
+Just replace `<pool>`, `<device-part1>` and `<device-part2>` with the pool name
and the two `/dev/disk/by-id/` paths to the partitions.
You can also add ZIL and cache separately.
@@ -527,8 +527,8 @@ process of the new disk has progressed.
# proxmox-boot-tool init <new disk's ESP> [grub]
----
-NOTE: `ESP` stands for EFI System Partition, which is setup as partition #2 on
-bootable disks setup by the {pve} installer since version 5.4. For details, see
+NOTE: `ESP` stands for EFI System Partition, which is set up as partition #2 on
+bootable disks when using the {pve} installer since version 5.4. For details, see
xref:sysboot_proxmox_boot_setup[Setting up a new partition for use as synced ESP].
NOTE: Make sure to pass 'grub' as mode to `proxmox-boot-tool init` if
@@ -541,7 +541,7 @@ especially if Secure Boot is enabled!
# grub-install <new disk>
----
NOTE: Plain GRUB is only used on systems installed with {pve} 6.3 or earlier,
-which have not been manually migrated to using `proxmox-boot-tool` yet.
+which have not been manually migrated to use `proxmox-boot-tool` yet.
Configure E-Mail Notification
--
2.39.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel