July 26, 2025Jul 26 Hello all, This one is a bit confusing, I have been here for a long time been a user and for the life of me I cant explain why a docker is writing directly to a single disk and ignoring share settings.For the primary share I have it setup toFill up101gb freeCache > ArrayYet most recently my disk 4 was left with 24kb free while I have a good number of disks with 100s GB free and a couple with 7tb free. I have double checked the shares, the disks, parmissions. On a whim I did update the OS to see if that corrected this issue. Nope. Im at a lose. tower-diagnostics-20250726-0017.zip
July 26, 2025Jul 26 Author Just to note, I tested NZB360 and behaved as it should, accessing the cache before any of the disks. TubeArchivest on the other hand is the one that is bypassing the share rules.Just spit balling here... If I have a share at /mnt/user/Media and I have a docker that accesses a file at /mnt/user/Media/YT/HiThere/. That docker should follow the rules set for the share at /mnt/user/Media... Correct? If that's not the case, it would explain what is happeningThoughts?
July 26, 2025Jul 26 Author Could this explain/fix the issue?"Disk Space ManagementstrikeInstallSupport ForumPin AppThis plugin was created mainly for those who use the split-level feature in Unraid. Due to how split level works, it will ignore the minimum free space setting and continue to move stuff to disks that are full/almost full. This is because split level tries to keep files and folders that belong together based on your split level setting on the same disk, and split level trumps all other settings. Even if there's little space left on the disk. So to combat this, this plugin will automatically move Movies and TV shows from disks that are below the threshold setting to the disk with the most free space available. It prioritizes to move movies first, then if no movies are found it will go to TV shows and move the shows with the fewest seasons first."
July 26, 2025Jul 26 Community Expert 1 hour ago, mathomas3 said:That docker should follow the rules set for the share at /mnt/user/Media... Correct?Correct1 hour ago, mathomas3 said:Could this explain/fix the issue?If you have a split level set for the share that could be the issue, since split level overrides allocation method.
July 26, 2025Jul 26 Author As far as I know... you have to set SOME split level of sorts... The verbage of this setting leaves you wondering why disk 4 is special...
July 26, 2025Jul 26 Community Expert Can’t see anything obvious to explain the behaviour.Could there be existing files that are growing in size after initial creation? Existing files are always amended/changed on their current disk and will not get moved if doing so breaks the Minimum Free Space setting.
July 27, 2025Jul 27 Community Expert Is the container moving data that is already on the array to that share or writing new data?
July 27, 2025Jul 27 Author 15 hours ago, JorgeB said:Is the container moving data that is already on the array to that share or writing new data?The container is writting new data af far as I know... Ill look at it closer
July 29, 2025Jul 29 Author Just adding notes to this as it seems to be a bug of sorts... disk 4 is holding steady with 69gb of free space... disk 5 has 103gb of free space... disk 6 has 20gb... disk 7 is currently being written to... and has 100gb of free space... why these files are bypassing the cache drive??? seeingly there is some logic happening, via docker restarts/reboots... today I moved unraid to a complete new system from the old R340 so yea... perhaps involving the TubeArchivest group is warrented at this moment
July 29, 2025Jul 29 Author hmmm... now TA has moved to hdd 8... 7 is under the 100gb window... so... it's kinda doing what it should but ignoring the cache disk? huh?
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.