Need ZFS Config Advice reddit / BSD ---------------------------------------------------------------------- darkempath · 2018-07-09 13:55 I'm building a home server (FreeBSD 11.2) and I've put two 8TB WD Reds in it. I'd like advice on how I should configure the reds. I have an M.2 drive for the system, and I wanted to create a separate pool for the two reds as purely storage. I want some level of redundancy, as well as the ability to add more storage to the pool down the track. Is there a way to get redundancy other than zRaid or mirroring? With the two 8TB drives, I'm happy to end up with only 8TB storage, especially if it means I can add drives later without needing to add two identical ones at a time. (I'm a hobbyist, not a professional, so please forgive any stupid question I ask!) My old server has a single 5TB drive in it. Once my new server is up and running, is there a way to add the 5TB drive to the storage pool to get 10.5TB of storage? (Out of a total of 21TB of physical drive space?) The storage will be used for TV shows and movies for Kodi, music for streaming, possibly Nextcloud data, some backups, some personal data, etc. Any advice would be much appreciated! (The machine is a Ryzen 5 with 16GB of RAM, 250GB M.2, Gbit network, headless server.) ---------------------------------------------------------------------- crest_ · 2018-07-09 14:18 ZFS pools stripe data over all VDEVs. To get redundancy in a pool each VDEV has to be redundant. ZFS has two ways to expand a pool: either replace all disks in a VDEV with larger ones (one disk at a time) or add new VDEVs to the pool. Matthew Ahrens is working on adding a thrird way (growing a RAID-Z VDEV by adding disks to it), but don't hold your breath waiting for it. If you want to grow your pool over time in affordable increments go with a ZFS pool of mirrors and add pairs of disks over time. The next question question is what to do with your SSD. If you want to use the pool as NAS sync write latency is very important so you probably want to use a small partition (ca. 1GB per 100MB/s write performance of your HDDs is enough) as SLOG. Putting the ZIL on a SSD instead of the HDDs reduces write latency a lot, but if you loose the SLOG you have to roll back the pool to the latest transaction which was written to the disks. This isn't a huge problem on a small home server, but it violates the D in ACID. To protect against this you can use two (smaller) SSDs and mirror the SLOG. Don't use a L2ARC. The memory required to index the L2ARC is better use for the normal ARC. ---------------------------------------------------------------------- darkempath · 2018-07-09 14:48 > If you want to grow your pool over time in affordable increments go with a ZFS pool of mirrors and add pairs of disks over time. *sigh* Yeah, I thought that would be the case. Thanks, you've confirmed what I thought my situation would be. My case has space for eight 3.5 inch drives, and I ensured my PSU could handle several drives, so I guess pairs it is! I'm not worried about my SSD. I'm backing up important stuff (e.g. mail, config files), so if it dies I can replace it, reinstall, and remount the storage pool. Just a day/evening of downtime. > Matthew Ahrens is working on adding a thrird way (growing a RAID-Z VDEV by adding disks to it), but don't hold your breath waiting for it. I'm really annoyed at myself about that. I never thought I was a ZFS expert, but I thought I'd read something about that being an existing option. D'oh! Thankyou for clarifying that for me. Of course, I've been doing lots of reading and considering options, but I wanted to make sure I wasn't missing or misunderstanding anything. You've been a great help! ---------------------------------------------------------------------- vermaden · 2018-07-10 05:19 You will also have to decide if you want to use full disk encryption with GELI below ZFS. As for the options, IMHO either do the 2 x 8TB ZFS mirror or 3 x 5TB RAIDZ (raid5) (8+8+5) on the GPT partitions and additional 2 x 3TB mirror from the renaming space of the two 8TB disks.