public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Matthias Heiserer <m.heiserer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 8/9] local-zfs: typo fix/better phrasing
Date: Fri, 18 Nov 2022 12:09:48 +0100	[thread overview]
Message-ID: <20221118110949.59298-8-m.heiserer@proxmox.com> (raw)
In-Reply-To: <20221118110949.59298-1-m.heiserer@proxmox.com>

Signed-off-by: Matthias Heiserer <m.heiserer@proxmox.com>
---
 local-zfs.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/local-zfs.adoc b/local-zfs.adoc
index 0fa06b0..34eb06b 100644
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -235,7 +235,7 @@ There are a few options to counter the increased use of space:
 The `volblocksize` property can only be set when creating a ZVOL. The default
 value can be changed in the storage configuration. When doing this, the guest
 needs to be tuned accordingly and depending on the use case, the problem of
-write amplification if just moved from the ZFS layer up to the guest.
+write amplification is just moved from the ZFS layer up to the guest.
 
 Using `ashift=9` when creating the pool can lead to bad
 performance, depending on the disks underneath, and cannot be changed later on.
@@ -406,8 +406,8 @@ As `<device>` it is possible to use more devices, like it's shown in
 Add cache and log to an existing pool
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-If you have a pool without cache and log. First partition the SSD in
-2 partition with `parted` or `gdisk`
+If you have a pool without cache and log, first create 2 partitions on the SSD
+with `parted` or `gdisk`.
 
 IMPORTANT: Always use GPT partition tables.
 
-- 
2.30.2





  parent reply	other threads:[~2022-11-18 11:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 11:09 [pve-devel] [PATCH docs 1/9] bibliography: update 404 link Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 2/9] package-repos: fix typos Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 3/9] network: fix typo Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 4/9] network: fix dead link Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 5/9] local-lvm: typo fix/better phrasing Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 6/9] local-zfs Remove SSD suggestion as it's outdated Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 7/9] local-zfs: rephrase ZFS RAID description Matthias Heiserer
2022-11-18 11:09 ` Matthias Heiserer [this message]
2022-11-18 11:09 ` [pve-devel] [PATCH docs 9/9] Update ExtJS version Matthias Heiserer
2022-11-18 12:03 ` [pve-devel] [PATCH docs 1/9] bibliography: update 404 link Thomas Lamprecht
2022-11-18 12:04 ` [pve-devel] applied-series: " 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=20221118110949.59298-8-m.heiserer@proxmox.com \
    --to=m.heiserer@proxmox.com \
    --cc=pve-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal