February 28, 20251 yr When I create files on the cache drive (/mnt/cache/), it seems to appear immediately on the array (/mnt/user/). I don't believe the mover is being invoked for this to happen. However, if I delete the cache version of the file, the array version is removed as well. I was under the impression files are created in cache, then show up on the array after the mover processes them and are removed from cache, however this doesn't seem to be the case here. The share of interest is set to cache (primary storage) --> array (secondary storage) with high water allocation method. Additionally, when I upgraded from Unraid version 6.2.10 to 7.0.0, files downloaded to cache weren't moving to array, invoking the mover did nothing. This problem resolved after downgrading back to 6.2.10, but the issue listed above is present. If someone could help me get the array data to remain when removed from cache, and potentially determine why the mover isn't working on version 7.0.0, I'd appreciate it. Edited February 28, 20251 yr by Jaeger9671 Didn't list what I actually needed help with
February 28, 20251 yr Community Expert /mnt/user/data will also show the pool data, only /mnt/user0 won't.
February 28, 20251 yr Community Expert 5 hours ago, Jaeger9671 said: and potentially determine why the mover isn't working on version 7.0.0, I'd appreciate it. Do you have the Mover Tuning plugin installed? If so it is probably a version that is not compatible with Unraid 7 so remove it. if it is not that then post diagnostics taken on Unraid 7 after trying to run mover.
February 28, 20251 yr Author Solution I ended up getting this resolved via Discord. Basically the mover wasn't moving because my array was half full and my share was configured to high water. I was seeing the file duplicated on /mnt/cache and /mnt/user because /mnt/user is a FUSE and /mnt/user0 is the actual array drive.
February 28, 20251 yr Community Expert 3 hours ago, Jaeger9671 said: I ended up getting this resolved via Discord. Basically the mover wasn't moving because my array was half full and my share was configured to high water. I was seeing the file duplicated on /mnt/cache and /mnt/user because /mnt/user is a FUSE and /mnt/user0 is the actual array drive. /mnt/user0 is not what you think it is, it's still FUSE but excludes pools such as cache, and any others you create. /mnt/disk1, /mnt/disk2, etc are the actual array drives. Also being 50% full doesn't make mover stop working. having duplicate files on both a pool and the array will prevent mover from running. Highwater is just a method in which unraid fills array drives, high water will still fill drives to 100%
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.