Comment

ZFS is a very robust choice for a NAS. Meant people, myself included, as well as hundreds of businesses across the globe, have used ZFS at scale for over a decade.

Attack the problem. Check your system logs, htop, zpool status.

When was the last time you ran a zpool scrub? Is there a scrub, or other zfs operation in progress? How many snapshots do you have? How much RAM vs disk space? Are you using ZFS deduplication? Compression?

source

Sort:hotnew top

Trincapinones@lemmy.world ⁨9⁩ ⁨months⁩ ago
I don’t even know what a zpool scrub is lol, do you have some resources to learn more about ZFS?

source
- Kata1yst@kbin.social ⁨9⁩ ⁨months⁩ ago
  Yeah, you should be scrubbing weekly or monthly, depending on how often you are using the data. Scrub basically touches each file and checks the checksums and fixes any errors it finds proactively. Basically preventative maintenance.
  https://manpages.ubuntu.com/manpages/jammy/man8/zpool-scrub.8.html
  
  Set that up in a cron job and check zpool status periodically.
  
  No dedup is good. LZ4 compression is good. RAM to disk ratio is generous.
  
  Check your disk's sector size and vdev ashift. On modern multi-TB HDDs you generally have a block size of 4k and want ashift=12. This being set improperly can lead to massive write amplification which will hurt throughput.
  https://www.high-availability.com/docs/ZFS-Tuning-Guide/
  
  How about snapshots? Do you have a bunch of old ones? I highly recommend setting up a snapshot manager to prune snapshots to just a working set (monthly keep 1-2, weekly keep 4, daily keep 6 etc) https://github.com/jimsalterjrs/sanoid
  
  And to parrot another insightful comment, I also recommend checking the disk health with SMART tests. In ZFS as a drive begins to fail the pool will get much slower as it constantly repairs the errors.
  
  source
  - BobsAccountant@lemmy.world ⁨9⁩ ⁨months⁩ ago
    Adding on to this:
    
    These are all great points, but I wanted to share something that I wish I’d known before I spun up my array… The configuration of your array matters a lot. I had originally chosen to use RAIDZ1 as it’s the most efficient with capacity while still offering a little fault tolerance. This was a mistake, but in my defense, the hard data on this really wasn’t distributed until long after I had moved my large (for me) dataset to the array. I really wish I had gone with a Striped Mirror configuration. The benefits are pretty overwhelming:
    
    Performance is better than even RAIDZ2, especially as individual disk size increases.
    
    Fault tolerance is better as you could have up to 50% of the disks fail, so long as one disk in a mirrored set remains functional.
    
    Fault recovery is better. With traditional arrays with distributed chunks, you have to resilver (rebuild) the entire array, requiring more time, costing performance and shortening the life of the unaffected drives.
    
    You can stripe mismatched sets of mirrored drives, so long as the mirrored set is identical, without having the array default to the size of the smallest member. This allows you to grow your array more organically, rather than having to replace every drive, one at a time, resilvering after each change.
    
    Yes, you pay for these gains with less usable space, but platter drives are getting cheaper and cheaper, the trade seems more worth it than ever.
    
    source
    Trincapinones@lemmy.world ⁨8⁩ ⁨months⁩ ago
    I don’t have any redundancy, my system has an SSD (the one being slow) and 2 500Gb HDDs, in the hdds I only have movies and shows so I don’t care is that goes bad and I have a lot of important personal stuff in the SSD but is new (6 months old) from crucial and I trust that because I don’t have the money to spare on another drive (+ electricity bills) and I trust that I’ll only lose 1-2 files if it goes bad because of the ZFS protection
    
    source
  - Trincapinones@lemmy.world ⁨8⁩ ⁨months⁩ ago
    Wow that’s a lot of info, thank you!
    
    source