deibit

Gracias, I guess I'm going to do the move, time to test the "unbalance" plugin (starting now...)

they were added around 2 years ago (if my mind doesn’t play tricks on me), I just didn’t pay attention to the error until now…

Sorry to revive this old thread, but I experience the same in 6.12.0-rc6 I get this very same error in 5 disks, 4 of them are 16TB and one of them is 12TB Is there a solution for this? I hope that the answer is not going to be to move 76TB-ish of data to another drive, reformat and recopy.... 😮

I see.. the challenge is to find the workaround with the least manual impact... since the file-move is automated inside a docker.. I guess I cannot use the workarounds 1, 3, 4, 5 or 6 That leaves me with workaround two.. that in the end means (if i want full automation) I must switch "Media" to use cache a primary, set the mover-action from cache->array and then rely on the mover to move the files from time to time. The main problem is that if I do a copy of files to the user share (as in to copy 1TB of files) then it's going to copy them to the cache first (or I need to manually switch the "primary storage" before doing the copy..). Either that or find a disk with enough space and to the move directly to the disk instead of using the user share... But ok.. I guess "it's what it's"..

Hey, I have read pretty much everything I could find, but I am still not able to implement what I "need" So.. I have a Share called "Media" Media primary Storage is "Array", and that's ok because I want that every new folder in "Media" is directly persisted in the Array I have a Share called "Downloads", This share is where the "complete" and "incomplete" sabnzbd folder are located. Primary storage is cache, secondary storage is Array and mover-action is array->cache The thing is.. when I move a file from "Downloads" to "Media" the file remains physically in the cache, the only way to move it physically from the cache is to temporary define "Media" to use the cache as primary, array as seconday, mover-action to cache->array and them run the mover. But to do it manually everytime is kind of a pain (not to mention how error prone this is) I am sure that there must be a simple way to do this.. what am I doing wrong? Thanks!