August 19, 20223 yr Would there be any unforeseen issues with this? The cache pool mode would be set to: Yes indicates that all new files and subdirectories should be written to the Cache disk/pool, provided enough free space exists on the Cache disk/pool. If there is insufficient space on the Cache disk/pool, then new files and directories are created on the array. When the mover is invoked, files and subdirectories are transferred off the Cache disk/pool and onto the array. Edited August 19, 20223 yr by taflix
August 19, 20223 yr Author 1 hour ago, itimpi said: This works fine. Thanks! This is great because now I can create 1 large cache pool and have my Shares share it. I don't have to worry about any one Share running out of cache storage. I don't see why this isn't more commonly used?
August 19, 20223 yr Community Expert 1 hour ago, taflix said: I don't see why this isn't more commonly used? That is actually the default setup... Some people with a lot of "download activity" like to separate things so as not to use the same storage for important data and unimportant in-progress downloads with the risk of the latter clogging the cache and causing issues for the former.
August 19, 20223 yr Community Expert 6 hours ago, taflix said: don't see why this isn't more commonly used? Anybody with a single pool is going to do that, some shares cache:only or cache:prefer, some cache:yes. Even with multiple pools I have multiple shares that use each.
August 19, 20223 yr Community Expert 3 hours ago, trurl said: some shares cache:only or cache:prefer This is what you should have for appdata, domains, system, so Docker/VM performance isn't impacted by slower array, and so array disks can spin down since these files are always open. I put these shares on my pool named "fast", a single 256G nvme as XFS with backups to the array. My "cache" pool is 2x500G SSD as btrfs raid1 for caching. Both pools get involved with downloads and postprocessing.
August 19, 20223 yr Author 6 hours ago, trurl said: This is what you should have for appdata, domains, system, so Docker/VM performance isn't impacted by slower array, and so array disks can spin down since these files are always open. I put these shares on my pool named "fast", a single 256G nvme as XFS with backups to the array. My "cache" pool is 2x500G SSD as btrfs raid1 for caching. Both pools get involved with downloads and postprocessing. Seriously, life changing for me. Thank you for sharing!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.