July 25, 2025Jul 25 I installed Jellyfin, only for my music dir. and my cache is now at 60% up from 10% used.I removed Jellyfin, but the bloat is all still there.I would like to remove whatever files (almost 690GB) are the cause, but I can not find them anywhere aFter drilling down though each file in the share, it shows nothing to remove.I trie dqdirstat but it does not show the file sizes.Any help sorting this out is appreciated. I thought a reboot may solve it but alas, no joy.
July 26, 2025Jul 26 Community Expert If you can't see what's using the space, you can use the mover to move data to the array or different pool until you find it, then move the the rest back.
July 26, 2025Jul 26 Community Expert You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs.
July 26, 2025Jul 26 Community Expert 3 hours ago, LordShad0w said:Would the info still be there after I rebooted?No one can answer that question until the files have been examined!
July 27, 2025Jul 27 Community Expert What is this share?t--p shareUseCache="only" # Share exists on cache, disk2, disk3, disk4, disk5, disk7It is set to only be on the cache for new files but has existing files on the main array. You might get a more useful pointer to where space is being used if you use something from the command line like du -h -d2 /mnt/cache
July 27, 2025Jul 27 Author It seems it is a share called backup_internal. It was taking up almost 500GB. I am not sure what created it, as the normal backup folder is there from unraid appdata backup which is simply called backup.For now I nuked it and will check to see if it comes back and what is creating it, if possible.big thank you to @itimpi for the command line advice. It immediately helped me find the space hogging share.
July 27, 2025Jul 27 Community Expert First thing I would is to Click on this spot:And use the built-in File Manager to look at the contents of this share on your cache drive. See if you can figure out what generated the files. (I would be suspecting a Docker Container.)Once you figure it out, Look at the Variables in the container and see if one of the points to share backup_internal. It will part of a path like /mnt/user or /mnt/cacheIF you can't figure it out, I would suggest looking at all your Docker containers and see which one has a variable pointing to that share.
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.