Hello, I recently switched to Unraid from Freenas. So far it has been quite a pleasant experience. One issue I am having is with the High Water fill method. It does not appear to be working properly on my Media share. I am currently injesting about 22TB worth of media and I have them going onto 4x8TB (SMR archive) drives. The drives are not filling to 50% before proceeding to the next drive. 8TB is the largest disk in my system so as I understand it they should fill until they have less than 4TB free space then move onto the next drive in the share with more than 4TB of free space. I have attached a picture of how they are currently filling. Also attached are my current share settings.

 

Can someone please shed some light as to what is happening?

 

Will Unraid start filling another disk if a write request takes too long on a drive? These archive drives do have some extra latency and reduced speeds.

 

Thanks

Lonnie

 

It has now gone back and started filling disk 3. After some fiddling it suddenly jumped over to disk 2 and filled that one past the 50% mark. Now however it refuses to write anything to disk 1, even if I set it to "Fill-Up" or "Most-Free". I have checked and double checked all settings to see if I am excluding disk 1 anywhere but I haven't come up with anything. The attached picture is where I am at now.

 

I thought maybe unraid was incorrectly reading the free space so I took the array offline and remounted it, I also rebooted the machine but it still refuses to write to disk 1. 

 

Does anyone have any suggestions?

 

Thanks

Lonnie

How is the split level set for the Media share?

Same as in the first post pictures."Automatically split any directory as required"

Sorry, didn't notice the screenshot, post your diagnostics.

Hmm... So i have my Media share that is ingesting data from "TV Shows" folder and "Movies" folder. The "TV Shows" folder did not exist on Disk 1 as it only had part of the Movies directory. I manually created the "TV Shows" directory through the Disk share and suddenly unraid started writing to that disk.

 

Here is the Diagnostic file anyways. I would still like to know why it wouldn't create the directory.

andromeda-diagnostics-20170307-0942.zip