Hey,

So came across a bit of an issue recently, added a ton of stuff to library (10tb or so) during which I noticed qbit would error a ton of stuff, I ignored them until others got finished but im at that point now, looked a bit more into it and found unraid shoved it all into a single disk, leaving it with 16mb free and still trying to write more to it.

the share is configured (or was, messing with settings now) to high water autolevel. it seems like its allocated my qbit to disk2 and doesnt care about splitting it even when the drive is physically full and ignoring minimum space (apparently thats expected behavior). Is there anyway for unraid to figure out "hey this drive is actually full, lets write elsewhere"?

For now I'm unbalancing data out of it to get through wave of new data but is this expected? should I change the library settings? I'm trying to change it to most free atm and see if that does anything.

pic of disks with previous settings, seems all over the place, disks sitting half empty while some are filled as much as possible

Also here's the kicker, qbit is set to pre-allocate space, it has 27.5tb allocated to a 12tb disk, surely this shouldnt be normal. unbalanced is going ot free up 19.7tb from 12tb disk lol.

Edited September 21, 2025Sep 21 by Mizerka

Note that split level overwrites allocation mode, so check that for the share you were writing to.

split level set to auto, has been set to high water previously, just moved it to most free now to see how it behaves. excluding my flash disks

moved out about 700gigs so far from disk2, unraid reports it as 3gb free now, so thats progress I guess and over allocation will be the issue, question is I suppose, how to prevent this moving foward.

If it's not the split level, it suggests something is writing/moving directly to the disk share.

yeah I considered that, but it seems fine, it will be a combination of qbit not allocating space properly, with a ton of data ingest and mover doing its best I suppose, but its still kinda wild it allowed it to get to that stage.

for future travelers I suppose, changing to most free and enabling a incomplete save path in qbit will force move a ton of stuff into the incomplete path at which point it will be moved into cache>array(most free), I ended up cancelling unbalanced job and letting qbit move the files over instead as it's aware of missing chunks better rather than moving empty data over for no reason. about halfway through re-enabled all services and its chugging along, from 600 down to 100 or so left to move, 12.6tb allocated so almost fixed, biggest issue is dealing with private trackers complaining about hnr while you fix stuff