Differences

This shows you the differences between two versions of the page.

--- workshop:06_persistent_volumes_content_trees [2026/07/22 13:43] – mc
+++ workshop:06_persistent_volumes_content_trees [2026/07/22 14:03] (current) – mc
@@ Line 54: / Line 54: @@
   * **Isolated per-VM volumes** — each app gets its own volume (no sharing, no error), or
   * **NFS / SMB share** — one app owns the volume and exports it; others mount it over a local network instance for live concurrent access.
+==== How to: install EVE with a ZFS persist pool ====
+There is **no in-place conversion** — ''/persist'' holds all node state, and its filesystem
+type is chosen at **install / first boot**. To get ZFS you must (re)install EVE with ZFS
+targeted from the start; changing an existing ext4 node means **wipe + reinstall + re-onboard**.
+ZFS is selected via a grub install variable in the installer's ''grub.cfg'' (in the
+''config'' / EFI partition of the install media, or baked into a custom EVE installer image):
+<code>
+eve_install_zfs_with_raid_level=none
+</code>
+Accepted values (default is ''none''):
+^ Value ^ Redundancy ^ ZFS layout / disks needed ^
+| ''none'' | **None** | single disk / stripe — no redundancy (use this for a single-disk box) |
+| ''raid1'' | Mirror | survives 1 disk loss — needs ≥2 disks |
+| ''raid5'' | RAIDZ1 | survives 1 disk loss — needs ≥3 disks |
+| ''raid6'' | RAIDZ2 | survives 2 disk losses — needs ≥4 disks |
+**Notes:**
+  * **''none'' is enough for multi-attach.** Multi-attach only needs ZFS *backing* (volumes become zvols); redundancy is irrelevant. On a single-disk node, ''none'' is the only option.
+  * There is **no** ''raid0'' / numeric ''0'' value — use ''none''.
+  * The variable also applies on **first boot of a live image**, not just a full installer — so baking it into the config makes first boot lay down a ZFS persist pool instead of ext4.
+  * Set it alongside the other install vars in the same ''grub.cfg'' (''eve_install_disk'', ''eve_persist_disk'', ''eve_install_server'').
+  * **Verify the variable/values against your EVE version** — install-var names have shifted across releases; check the ''grub.cfg'' on your current install media or EVE's ''docs/BOOTING.md''.
+After the ZFS install completes and the node re-onboards, block-storage volumes are zvols
+and ''multiattach = true'' + ''MULTIREAD_SINGLEWRITE'' will work.
 ===== Do the VMs have to stay one-reader / one-writer? =====