Jump to content

Mover possible weird behavior


Recommended Posts

Hey.

First of all, I'm kind of new to unraid therefore please explain with a bit more detail the possible solutions :)
Version: 6.10.0-rc2 

The "issue" which I'm facing is that for example I've had files on the disk cache and then when they got moved to the array I've noticed this stats: 

Location                |       Before move  |  After move  |   Difference/Moved
Array free(Disk 1):   |         ~95GB        |      10GB       |      85GB
Cache free:            |           80GB        |     110GB       |      -30GB

*Docker and Vm`s were disabled before the move followed by a server reboot and then the Mover was invoked.

I'm can`t understand why the GB difference.

Edited by obi-WAN-kenobi
Added a mention (*)
Link to comment
3 hours ago, JonathanM said:

Does this help?

https://wiki.unraid.net/Manual/Storage_Management#Moving_files_between_a_Pool_and_the_array

 

Mover has many jobs, it can put files ON the cache as well as take them off.

Im familiar with how mover works. I just though not to add to much text to the post in order to keep it simple and easy to understand :)
They are all set to Yes except the Appdata which only on cache.

What didn't make sense to me is that Mover moved 85GB from cache to array but the "moved" data didn't free up the Cache space.
Put in different words, 55GB got moved but in same time remained on cache. 

Edited by obi-WAN-kenobi
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...