From 943d545bb9d71d6faaa57502daeaca158e7ed799 Mon Sep 17 00:00:00 2001
From: eater <=@eater.me>
Date: Fri, 23 Oct 2020 19:04:25 +0200
Subject: [PATCH] explain wwns

---
 data/posts/pre-flight-nas-checklist.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data/posts/pre-flight-nas-checklist.md b/data/posts/pre-flight-nas-checklist.md
index 7849453..373792e 100644
--- a/data/posts/pre-flight-nas-checklist.md
+++ b/data/posts/pre-flight-nas-checklist.md
@@ -157,7 +157,7 @@ Well, you set up Linux or FreeBSD or what you wanna run on your NAS and do what
 
 but here's a few tips & tricks I've learned.
 
-- Put a label with the WWN on your disk caddy or enclosure. this will save you time figuring out which disk is which (you can find the WWN of your disk either by `ls /dev/disk/by-id/wwn*` or `lsblk -o NAME,WWN`)
+- Put a label with the WWN on your disk caddy or enclosure. this will save you time figuring out which disk is which (you can find the WWN of your disk either by `ls /dev/disk/by-id/wwn*` or `lsblk -o NAME,WWN`), a WWN is a completely unique number for that disk, which means it'll always be the same, everywhere, and if you're lucky it's even printed on the disk itself!
 - If you're planning to expand set a warning at 60% of pool usage, and start planning for expansion (buying disks etc.), why? at 80% ZFS in particular will -notably- degrade in performance, and if you're early your rebalancing task will be less load on your other disks too. So make sure you have new disks in your pool before hitting 80%!
 - Make sure you have `smartd` enabled and a monitoring system for it, so you can respond as soon as possible to a failing disk
 - If you're planning to have a Big Tank™ try to divide your disk into at least 2 subvolumes, 1 part that you want to backup, and 1 part that's okay to lose. This will allow you to have a small backup server, but still have backups.