Hello,

 

After growing up the size of the docker.img then I see that image is still with the old size and no new one.

 

However if I explore the content of the cache drive where I put some files in it, then those files are hidden because I can't find them.

 

Can you elaborate a bit more with some screenshots

Hello,

 

Sorry for later reply. At first when you increase the size from 10GB to 15GB of the docker image then it reports fine like this.

 

 

But on the next image if you are explore the cache drive from windows network on LAN then you'll see that it reports the old size, 10GB.

 

 

At final step, if you're on cpanel from web and explore the share folder then you'll see like the next image that the folder named "scene" is still there with many files inside. And actually it gets the new total size from docker image.

 

 

I think the problem were on setting the windows network adress again.

 

Still don't entirely understand what you are saying, but why do you have a folder named cache on your cache drive? And of course, any folder at the top level of cache or any array disk is automatically a user share, so that means you have a user share named cache. Very confusing, and this would also be confusing to Windows if you have also shared the cache disk, since SMB will not be able to show them both.

 

I suspect you have some docker misconfigured and it is creating the cache folder. Post a screenshot of your Docker page showing the volume mappings.

Hello trurl,

 

The reason that there's a folder named a cache drive it seems a problem with a share settings. On Disk shares, I have disabled all disks shares but if I want to turn off or disable the cache disk then I can't disable it, so it always on and not respond if I try to turn off and apply the settings . Maybe the problem was with this.

 

 

Here is the docker page config, so I only have transmission for torrents.

 

You actually have a folder named cache on your cache drive. This causes unRAID to create a user share named cache because all top level folders on cache drive or any array drive is automatically a user share named for the folder. Don't know how it got there but you should get rid of it.

 

In linux, this is /mnt/cache/cache, which unRAID user shares also shows as /mnt/user/cache.

SOLVED!!!

 

Thanks trurl, I resolved this issue by removing this cache folder. Now I see the content files on the cache share fine and no other anomally were found it.

 

thanks for all.