October 19, 20232 yr I apologize, I know this is an often discussed topic, and I felt like I had a pretty good understanding of how the cache and the mover work. But now I'm a bit confused. I noticed that a few of my shares had the yellow warning "Some or all files not protected." Their cache setting is set to "No", so I assumed that meant that writes to those shares would never go to cache. The mover won't move anything on them. But I drill into my cache drive, and there are a bunch of files from those shares on cache. Most are files that I have added to that share pretty recently. So with it set to "No", they are stuck there until I set cache to "Yes", and run the mover. Any idea how files from those shares got to cache with it set to no? I guess I should just leave them set to Yes anyway, and then it will just use the cache, but they'll get moved to the array every day? Is my assumption about the "no" setting incorrect? It must be because I thought with it set to no, it would just never use cache for those shares. I turn cache to Yes on that share, run the mover, and it moves the files as expected, and the share goes green. Am I misunderstanding the "no" setting on cache?
October 19, 20232 yr Community Expert If files get onto the cache for any reason then with the No setting they are left there as with that setting mover ignores cache.
October 19, 20232 yr Author 4 minutes ago, itimpi said: If files get onto the cache for any reason then with the No setting they are left there as with that setting mover ignores cache. Right, I figured as much, I guess I was just trying to figure out how they got there in the first place. Here's how the flow went: The files were downloaded to a share that is set to Cache: Yes. Then from there on the command line, I did a move command and moved them to the other share that has Cache: No. I'm wondering if that's how why they were in cache. Either way, I'm just going to set those shares to Cache: Yes, because I don't want them sticking around in cache. Seems so backwards lol. Edited October 19, 20232 yr by paqman
October 19, 20232 yr Community Expert Solution If you used move from the command line then you probably encountered the behaviour described in the Caution in this section of the online manual.
October 19, 20232 yr Author 6 minutes ago, itimpi said: If you used move from the command line then you probably encountered the behaviour described in the Caution in this section of the online manual. Ah, that makes a lot of sense. I think that's exactly what's going on here. I was using the CLI using the mv command to move the files from one share to another. It is definitely just renaming the path, because it is instantaneous, no copying going on. I guess the preferred way to avoid this would be to use a file system explorer like krusader or something? (Or use the copy command, and then delete the file) If I just set all those shares to Cache: Yes, can I just continue doing it the way I have been, and it will clean them up and move them off cache daily? I like that in the moment, the move is quick and easy, with it then moving the files later for me in the middle of the night. Just making sure there aren't any other drawbacks to moving them on the CLI like that. Edited October 19, 20232 yr by paqman
October 19, 20232 yr Community Expert If you install the Dynamix File Manager plugin and use that for file management it will protect you from this behaviour.
October 19, 20232 yr Author 12 minutes ago, itimpi said: If you install the Dynamix File Manager plugin and use that for file management it will protect you from this behaviour. Thanks a bunch, appreciate the help.
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.