It's possible this issue started between 6.6.1 and 6.6.3. I only just noticed that my cache drive isn't being written to and I'm on 6.6.3 now. I checked the share setting for "media" and it's set to "yes" for the Use Cache Disk setting. It's also setup in the global share settings. It had been working since I started using Unraid about a year ago I think. Not sure what to try as I believe I've looked up all I can as far as settings go to play around with. 

 

Thanks in advance!

Tools - Diagnostics. Attach complete zip to your next post.

Attached.

tower-diagnostics-20181106-1935.zip

Nothing obvious to me in diagnostics. What evidence do you have that it isn't using cache? How are you writing to the share?

I upload movies the same way I always have, using WinSCP to FTP to my server in the basement. I go to User0 and my media folder, and then the appropriate subfolder. In the past, this would go to the cache drive before it ran its process at some early hour in the morning to move media files from cache to disk. I upload stuff now, and there's nothing new on the cache drive, it just sits at its same used space amount and I see Disk 2 constantly updating the number of writes while I'm uploading. 

At least I think it's always been User0. Point is, it's not disk1, disk2, disk3, or disk4 as I know those write directly to disk. Maybe I should try writing to User instead of User0.

20 minutes ago, BioHazardous said:

At least I think it's always been User0. Point is, it's not disk1, disk2, disk3, or disk4 as I know those write directly to disk. Maybe I should try writing to User instead of User0.

Bingo. User0 is everything EXCEPT the cache drive.

As has been mentioned User0 includes all files/directories on the data disks in a share, not including the cache disk.

 

The reason that User0 exists is specifically to help implement the ‘mover’ functionality.

 

If a share is set to cache=yes, then any files in a share on the cache disk are moved by mover to the share in User0;  as the cache disk is not included this has the effect of moving the files from the cache disk to the data disks.

 

Similarly, if a share is set to cache=prefer then files are moved from User0 to the cache disk.

 

For ‘normal’ usage you should use the shares under User which includes files/directories on all data disks and the cache disk in a share.

6 hours ago, remotevisitor said:

The reason that User0 exists is specifically to help implement the ‘mover’ functionality.

Actually, it isn't needed for that purpose any longer since the mover was rewritten. user0 was briefly removed but reinstated after users requested it. I remember Tom making a wry comment at the time but can't find the link at the moment.

Thanks for the help!  I'm not sure why I didn't try that variable before coming here. I think it was when I had done one of the updates, WinSCP said the folder I was in didn't exist anymore, and I had to navigate back from root, and I must have had it in my head that it was User0.