proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-05-02 20:01:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix typos in local-zfs.adoc

Browse Source 
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
This commit is contained in:
Fabian Ebner 2019-09-02 11:19:51 +02:00 committed by Thomas Lamprecht
parent d5c3a54af9
commit 5dfeeece54
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
local-zfs.adoc
View File

@ -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 .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` 2 partition with `parted` or `gdisk`
IMPORTANT: Always use GPT partition tables. 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 comes with an event daemon, which monitors events generated by the
ZFS kernel module. The daemon can also send emails on ZFS events like 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`: 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`. unlocking on boot to `zfs load-key`.
WARNING: Establish and test a backup procedure before enabling encryption of 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. lost, accessing the encrypted data is no longer possible.
Encryption needs to be setup when creating datasets/zvols, and is inherited by Encryption needs to be setup when creating datasets/zvols, and is inherited by