So when I made my "appdata" share on the cache drive I selected the wrong option and now I have the share on disks when it should only live on the SSD.

 

If I change the option from....

 

Use cache disk: Yes

 

To..

 

Use cache disk: only

 

Will it remove the files from the spinning disks and move it back to the SSD? or will it for ever be split between them and new files be written ONLY to the SSD.

 

Or is it worth just making a copy of all the files in "appdata", then nuke the share and copy back to the newly created SSD ONLY. The cache was only to be used for Docker apps and temp folder for downloads.

Answer is no and no.

Changing it to cache only won't move the data.

However, you don't need to "nuke" the share to move the data over.

 

Just ssh in, run mc and move the data from diskx to cache.

Make sure you move from the disk and NOT the share.

 

Will it remove the files from the spinning disks and move it back to the SSD? or will it for ever be split between them and new files be written ONLY to the SSD.

No... It will only affect new files being written

 

Or is it worth just making a copy of all the files in "appdata", then nuke the share and copy back to the newly created SSD ONLY. The cache was only to be used for Docker apps and temp folder for downloads.

Depends.

 

The absolute ideal solution is to completely wipe the appdata folder and start again from scratch.  This is because of a symlink issue where if the files exist on the array, strange things happen.

 

If you cannot live with wiping the appdata folder completely clean, then yes, copy the files to a temp location, nuke the folder, and then copy them back.  But, many of the weird little issues with various apps (particularily Plex) are because of symlink issues.

 

Additionally, on each and every one of your docker templates, make sure that the /config folder is mapped to /mnt/cache/appdata/... and NOT to /mnt/user/appdata...  (You have to do this in addition to setting the appdata folder to be cache only for the symlink thingy)

 

Will it remove the files from the spinning disks and move it back to the SSD? or will it for ever be split between them and new files be written ONLY to the SSD.

No... It will only affect new files being written

 

Or is it worth just making a copy of all the files in "appdata", then nuke the share and copy back to the newly created SSD ONLY. The cache was only to be used for Docker apps and temp folder for downloads.

Depends.

 

The absolute ideal solution is to completely wipe the appdata folder and start again from scratch.  This is because of a symlink issue where if the files exist on the array, strange things happen.

 

If you cannot live with wiping the appdata folder completely clean, then yes, copy the files to a temp location, nuke the folder, and then copy them back.  But, many of the weird little issues with various apps (particularily Plex) are because of symlink issues.

 

Additionally, on each and every one of your docker templates, make sure that the /config folder is mapped to /mnt/cache/appdata/... and NOT to /mnt/user/appdata...  (You have to do this in addition to setting the appdata folder to be cache only for the symlink thingy)

 

Thanks for the info. I will be doing a copy of critical info like config/db of my apps then nuke and setup again. I went and checked to see my app config location and I did in fact have it as /mnt/user/appdata so I think a clean start will be the best bet.

 

Also doing a clean start will mean I avoid symlink issues, and I sure don't want to have to deal with that type of drama.