[pve-devel] applied: [PATCH pve-docs 02/12] Fix typos in local-zfs.adoc

Thomas Lamprecht t.lamprecht at proxmox.com
Mon Sep 2 12:05:25 CEST 2019


On 9/2/19 11:19 AM, Fabian Ebner wrote:
> Signed-off-by: Fabian Ebner <f.ebner at proxmox.com>
> ---
>  local-zfs.adoc | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/local-zfs.adoc b/local-zfs.adoc
> index af330e1..b4fb7db 100644
> --- a/local-zfs.adoc
> +++ b/local-zfs.adoc
> @@ -236,7 +236,7 @@ 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 an pool without cache and log. First partition the SSD in
> +If you have a pool without cache and log. First partition the SSD in
>  2 partition with `parted` or `gdisk`
>  
>  IMPORTANT: Always use GPT partition tables.
> @@ -269,7 +269,7 @@ Activate E-Mail Notification
>  
>  ZFS comes with an event daemon, which monitors events generated by the
>  ZFS kernel module. The daemon can also send emails on ZFS events like
> -pool errors. Newer ZFS packages ships the daemon in a separate package,
> +pool errors. Newer ZFS packages ship the daemon in a separate package,
>  and you can install it using `apt-get`:
>  
>  ----
> @@ -381,7 +381,7 @@ booting, or to write a custom unit to pass the key material needed for
>  unlocking on boot to `zfs load-key`.
>  
>  WARNING: Establish and test a backup procedure before enabling encryption of
> -production data.If the associated key material/passphrase/keyfile has been
> +production data. If the associated key material/passphrase/keyfile has been
>  lost, accessing the encrypted data is no longer possible.
>  
>  Encryption needs to be setup when creating datasets/zvols, and is inherited by
> 

applied, thanks!




More information about the pve-devel mailing list