November 13, 20232 yr Hi Everyone, I ran into two issues. Hoping you guys can help out. 1. Cache Size: Cache used and free are reported incorrectly (or I am not understanding something correctly). It says 33GB in use. I have moved all my shares settings to Cache -> Array and run the mover. I waited for several hours 10-12 hours for it to finish. So majority of the data should not be there. However, when I goto the share page it shows my virtual machine folders in cache. Here is the issue it says the .img single file in this folder is 68.7GB and it is on cache. So why is it showing 33GB on the main's page. Please look at the images attached to the post. 2. Docker: I moved from docker image to directory. Works perfectly for me. Did a clean reboot but when unraid came back online. Docker wasnt enabled and when I tried to enable it was set to docker image rather than the directory. Just wondering what could of have caused that to happen? Please find my diagnostic attached to the post. Edited November 13, 20232 yr by UWK removed the comment around diagnostic. Cant download it. browser crashes by saying out of memory.
November 13, 20232 yr Community Expert 1) Disable the VM service if you want VM files to be moved 2) You don't want appdata/system to go to the array or performance will be trash, and you don't want mover to touch the system share, especially not if using Docker folder.
November 13, 20232 yr Author Hey Kilrah. Thanks for the prompt response. The reason I did the move was temporary to sort out why the usage is not being reported correctly. I am going to set the system to cache and move others back to cache. The issue however, is the virtual machine which is 68.7GB on cache but on the main page cache says on 30GB used. These aren't adding up. I know I was previously using 200+Gb on cache but it was reporting 70GB only.
November 13, 20232 yr Community Expert VM disk images are sparse files, space is only allocated as necessary. In the file listing you see the apparent size which is how big you set that vdisk to be i.e. the max size it could grow to, but it's a sparse file and is only currently using the 30 or such on the disk.
November 13, 20232 yr Author Ahh that makes sense! Thanks Kilrah. Let me move the necessary files to cache again and see if the reported and shown adds up :). Any guidance on the second issue why the docker after reboot messed up?
November 13, 20232 yr Community Expert Can't really say with the info given, maybe the wrong path was supplied, mover was run on that share and messed things up, docker service was never started with the folder setting in the first place,... Wouldn't recommend folder personally. Edited November 13, 20232 yr by Kilrah
November 15, 20232 yr Author So once I changed all of the shared that should be on Cache and ran mover again. I let it ran for 1 day and nothing happened. The used disk drive size remained the same. I rebooted the system, shutdown the docker and ran it to no avail. Attaching diagnostics. If someone can please look and help me fix whatever I am doing wrong. tower-diagnostics-20231115-1514.zip Edited November 15, 20232 yr by UWK
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.