I have a share setup called TV, its allowed to put data on all disks apart from disk 7. In the share I've put "disk7" in the excluded disk input field. The included disk field is blank.

 

However (despite rebooting and restating the array) its still filling this disk first. I have taken all the data off this disk, manually, deleted the folder and then restarted the array.

I never use the excluded, I always put mine in the included field, you could try that.

I've implemented that but its still insisting on putting some content on there. There is a parity check running so I'm wondering if its rebuilding because the parity says one thing and the disk says another.

 

Can you use the SAMBA share to remove content ie \\IP.OF.MACHINE\disk7 ?

 

EDIT

Scrap that this is new files coming in from SabNZBd via Sickbeard, SickBeard is running a post processing script as well. The disks are now setup to include everything but 7 and exclude 7. However its still writing to 7

Think I've managed to at least solve the requirement (rather than the issue) by taking the disk completely out of the array and using SNAP to mount it.

 

Previously I'd been unable to find out how to auto-mount this on a reboot but subsequently found out you can do this using "snap.sh -ms <share_name>".

Can you post a screen shot of the share settings?