adminmat Posted December 21, 2020 Share Posted December 21, 2020 I've heard NextCloud constantly runs an indexing process causing constant reads that will keep your disk spinning. Is it bad practice to set nextcloud's data share to be on the Cache only or on an Unassigned Devices SSD? And I would back that data up to the array later? Quote Link to comment
extinct_waffle Posted February 24, 2021 Share Posted February 24, 2021 This is the problem I am currently having also. I had it only on the cache for a while, but a) it just filled it up far too quickly, and b) nothing was protected (I'm running a single cache drive). I've switched it to the array but as you say, it just keeps things spinning all the time, which is something that I want to avoid. Did you find a solution? Quote Link to comment
Hoopster Posted February 24, 2021 Share Posted February 24, 2021 With version 6.9.0 this becomes easier to manage. With 6.8.3 and older you can have a cache pool with multiple SSDs for redundancy in a BRTFS RAID 1 configurations. However, you can have only one cache pool so anything using cache goes there such as appdata, etc.. In 6.9.0 you can have multiple cache pools and you can assign different pools (could still just be one SSDs) to different shares. In this scenario, you could have a cache pool for general use which may be a single or multiple disks and you could have another cache pool for NextCloud use only with a cache-only share. Again, if you want redundancy, it could be a RAID1 pool. An unassigned devices SSD is another option but you don't have redundancy with that configuration. Quote Link to comment
Recommended Posts
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.