Specific computer only writes to 1 disk (it's not allocation method)

[Giggleanthropisticon]

unraid 6.12.11

allocation method: tried high water and most free

 

I have a 9 disk array all with 10.1TB free space (except 1 with 7.19TB free). it was running on "most free" allocation method. The array has been working as intended for nearly a year, until I estimate about a couple months ago, 1 specific computer only writes to disk 4 in the array. All other computers write correctly to array, except this 1 machine. The affected machine now refuses to write because the target drive is now full, confirming it won't simply move to the next drive. Client machines are all Windows.

I tried rebooting unraid and the client of course. Tried changing allocation method to high water + reboot as well. I'm so mystified that I haven't really tried anything else yet since I'm already at a loss.

diagnostics-20240814-1920.zip

Edited August 15 by Giggleanthropisticon
Attaching diagnostics

[trurl]

Attach Diagnostics to your NEXT post in this thread. 

[Giggleanthropisticon]

Attached

diagnostics-20240814-1920.zip

Edited August 15 by Giggleanthropisticon

[JorgeB]

Which share is that server writing to?

[itimpi]

.. and what is the full path?    The share anonymised as P———e has a Split level setting of 2 so this might be the issue as Split Level over-rides Allocation level if there is any contention between them about which drive to use.

[Giggleanthropisticon]

\\192.168.50.109\PlexShare\MediaHub Downloads

 

I have another computer that currently writes to the share effectively, as-is

[Giggleanthropisticon]

I was wrong and you're right about the split level. I tried writing again from the computer that used to be correctly writing to other drives a few days ago. It's now having the same "drive full" issue as well. I changed the split level to 4 and it's now writing. Thank you a bunch for your time.

Would you recommend simply setting to automatic split, instead of specifying a level?

[trurl]

I never bother with split level, and always use Highwater. This will usually send files that are written together to the same disk anyway, and the only penalty of having some files on a different disk is spinup delay.