diff options
| author | Jan Tuomi <jan@jantuomi.fi> | 2026-01-02 17:58:37 +0200 |
|---|---|---|
| committer | Jan Tuomi <jan@jantuomi.fi> | 2026-01-02 17:58:37 +0200 |
| commit | 7aff1f399ebfe289ed9ec8f38342f5d25eb60677 (patch) | |
| tree | 78dea9e4ec9598899320eeddd91bf700ccd0cad8 /content | |
| parent | c3502798f3dfc796a2569a04f7f561576df55be7 (diff) | |
Fix link
Diffstat (limited to 'content')
| -rw-r--r-- | content/posts/home-server-part-3.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/posts/home-server-part-3.md b/content/posts/home-server-part-3.md index b650d0f..456ee2a 100644 --- a/content/posts/home-server-part-3.md +++ b/content/posts/home-server-part-3.md @@ -37,7 +37,7 @@ Using the install wizard, I set up the system following my rough plan. And here You might notice that I bought 4 x 1 TB of NVMe disks, but `fastfetch` is only showing ~2TB. That's because I set up the disks into a "RAID 1+0" configuration: -{{ fig(src="/files/pursotin_raidz.svg", alt="A "RAID 1+0" configuration") }} +{{ fig(src="/files/pursotin_raidz.svg", alt='A "RAID 1+0" configuration') }} RAID 1+0 is a combination of two RAID levels. RAID 1, or _mirror_, consumes two disks to produce one virtual disk that has the capacity of only one physical disk but can withstand the loss of either one. ZFS can automatically heal missing data in a member of a mirror by copying it over from the healthy member. RAID 0, or _stripe_, consumes two disks to produce a disk that has the capacity of the sum of its member capacities as well as double I/O speed, but fails if either member disk fails. The combination of these is a useful way to get increased speed and increased durability at the price of half your raw capacity. |