jim_my

Do I have something set up wrong then? The files shouldn't already be on my array if they're going to cache first. Right now I have it set up as primary storage = cache, then mover action cache -> array. I don't see how the files would already be on the array as all of the files on my cache are newly downloaded files that would have never been on my array. When this first started happening a couple weeks ago, I tried shutting down my docker and vms and manually using terminal to move the files from my cache pool to one of my array disks directly, and that cleared all the space on my cache drive, but now a couple weeks later my cache drive is once again sitting at 99% filled (all new data, not something that would have been on the array already) with those logs. I just don't get why it was working fine before, and then I changed my cache drives and now this is happening.

Recently I made some hardware upgrades and added storage to my server. Since then I can't get mover to move files from my cache to my array. It just fills the cache drive to 100% and then adds new files directly to the array. Mover logs says "files exists" when I run it for seemingly every file on the cache drive. This makes me think that mover is copying files instead of moving, but I'm not sure if that's even possible, and I'm sure how to fix this. I tried new perms already as well as the mover tuning plugin. I originally had the mover tuning plugin, but uninstalled it to see if it would fix my issue. Diagnostics are attached. Thanks! tower-diagnostics-20231023-1204.zip