Notes based on this excellent Space Invader One video
Where To Store Shares
On Cache (prefer
)
appdata
: houses our docker’s container configuration contentdomains
: houses our VM’s datasystem
: houses our docker’sdocker.img
and our VM’slibvrt.img
On Array And Cache (yes
)
downloads
On Array Only
- any other shares you don’t often write to
- example:
media
shares
- example:
Share “Use cache disk” Settings
No
: Only stored on array.Yes
: Keep on the cache but also on the array.Only
: Only stored on the cache, never moved to the array.Prefer
: Will store on the cache, if the cache is full will move to the array. If you do not have a cache drive, will store on the array, and if a cache becomes available the data will move to the cache.
Installing Cache Drive(s)
- switch all the shares that you wish to store on the cache drive to
Prefer
, before installing the drive(s). Its possible this option is unavailable right now. if that’s true, just skip this step and we’ll cover it again later. - shut down the server
- physically install your cache drive(s)
- boot up the server
- stop the array
- under “Pool Devices” for each device, click a new slot and select a device from the drop down
- start the array
- under “array operations” check off the “Yes, I want to do this” under “Format” which will format all unmountable disks, which should be our N new cache drives
- Be sure to double check that the disks listed under “Unmountable disk present” are the expected cache drive(s)
- If you didn’t do step one, (as it was unavailable), set the shares you want to set to be on the cache now. See the above section for my advice on which shares should leverage the cache.
- Stop Docker and the VM service
- Click “Move” which will move all the shares intended to be on the cache, on to the cache. We stop Docker and the VM service, as there are many files that cannot be moved when in use. (Settings -> Docker -> Enable Docker set to “no”)
If you installed more than one drive, by default they’ll be in RAID 1, giving you a redundancy incase one disk dies. This is my preferred method instead of increasing performance with striping but losing redundancy
Depending on the size of your shares, this can take a while. It took about 3.5 hours for my ~80 GB of data to be moved to the cache.