Spaceherpe Posted January 6, 2018 Share Posted January 6, 2018 I am 100% sure that this question has already been asked and answered, but with so many threads, finding it has proven difficult... Anyways, here goes... I am running 3.6.4 due to issues with 3.6.5 and the power down/reboot function looping. That being said, my system consists of 3 (4tb storage) drives, 1 (4tb) parity and 1 (256gb ssd) cache drive. the current settings for my shares have system, appdata and domains in the "prefere" position for the cache drive. all other drives are listed in the "no" position. When I send files to the server wirelessly from another computer they are written directly to the storage discs instead of the cache and moved later by the mover. I am unsure what setting I have incorrectly set that is not allowing added files to be sent to the cache drive and moved later? Lastly, the server is primarily used for my Plex data library. I am afraid to list the plex share in any other configuration for fear of messing something up on the server. Any help with this would be greatly appreciated and thank you for all that you do for the community! Array Devices Device Identification Temp. Reads Writes Errors FS Size Used Free View Parity WDC_WD40EFRX-68N32N0_WD-WCC7K0XNARD3 - 4 TB (sdd) 72 F 265,161 265,384 0 Disk 1 WDC_WD40EFRX-68N32N0_WD-WCC7K3KS33U9 - 4 TB (sdc) 88 F 1,149,841 277,801 0 xfs 4 TB 2.98 TB 1.02 TB Disk 2 WDC_WD40EFRX-68N32N0_WD-WCC7K2EFJ56K - 4 TB (sdb) 90 F 944,833 73,378 0 xfs 4 TB 2.43 TB 1.57 TB Disk 3 WDC_WD40EFRX-68N32N0_WD-WCC7K6XATD2R - 4 TB (sde) 84 F 85,488 55 0 xfs 4 TB 2 TB 2 TB Total Array of four devices 83 F 2,445,323 616,618 0 12.0 TB 7.41 TB 4.59 TB Cache Devices Device Identification Temp. Reads Writes Errors FS Size Used Free View Cache SAMSUNG_470_Series_SSD_S0MTNEAB502605 - 256 GB (sdf) 84 F 499,421 2,658,477 0 btrfs 256 GB 16.4 GB 240 GB Boot Device Device Identification Temp. Reads Writes Errors FS Size Used Free View Flash v125w - 4.01 GB (sda) * 342 84 0 vfat 4 GB 176 MB 3.83 GB tower-diagnostics-20180105-2328.zip Quote Link to comment
JorgeB Posted January 6, 2018 Share Posted January 6, 2018 Change use cache to "yes" for the shares you want to go to the cache device before being moved to the array. 1 Quote Link to comment
Spaceherpe Posted January 6, 2018 Author Share Posted January 6, 2018 Done. Thank you Quote Link to comment
Spaceherpe Posted January 6, 2018 Author Share Posted January 6, 2018 Additional question. what is the difference between yes, no, prefer for cache? Quote Link to comment
itimpi Posted January 6, 2018 Share Posted January 6, 2018 5 minutes ago, Spaceherpe said: Additional question. what is the difference between yes, no, prefer for cache? Turn on the help in the GUI - it will explain what each setting means. 1 Quote Link to comment
Spaceherpe Posted January 6, 2018 Author Share Posted January 6, 2018 Thank you Quote Link to comment
goni05 Posted March 16, 2021 Share Posted March 16, 2021 Quote Specify whether new files and directories written on the share can be written onto the Cache disk/pool if present. This setting also affects mover behavior. No prohibits new files and subdirectories from being written onto the Cache disk/pool. Mover will take no action so any existing files for this share that are on the cache are left there. 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. Only indicates that all new files and subdirectories must be writen to the Cache disk/pool. If there is insufficient free space on the Cache disk/pool, create operations will fail with out of space status. Mover will take no action so any existing files for this share that are on the array are left there. Prefer 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 array and onto the Cache disk/pool. NOTE: Mover will never move any files that are currently in use. This means if you want to move files associated with system services such as Docker or VMs then you need to disable these services while mover is running. So those are the definitions. I have a question on how this should behave, because the definitions and the behavior don't align. I am running 6.9.0-rc2, and I have a share with the Use Cache Pool setting set to Yes. I have it setup as a SMB share, and have been attempting to copy over an archive into my array (array is 14TB - data copying is 5TB, cache disk is 1TB), but Windows keeps failing the copy process after it fills up the cache drive stating There is not enough space on [share name]. According to the definition, if the cache drive were to run out of space, then why does it not start writing over to the array? The ONLY thing I can think of is that the write starts, and when the cache runs out of space, the file it's attempting to write to fails, and then Windows just stops writing any further with the error message. Even when I attempted to Try Again, it failed again. Am I missing something, or should Unraid just handle this? Quote Link to comment
JorgeB Posted March 16, 2021 Share Posted March 16, 2021 7 hours ago, goni05 said: Am I missing something, or should Unraid just handle this? Set the share's minimum free space to about twice the largest file you expect to copy there. Quote Link to comment
goni05 Posted March 17, 2021 Share Posted March 17, 2021 Thanks. I knew i was missing something obvious. I thought that setting was related to the allocation method, but now it makes perfect sense. 1 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.