February 21, 20179 yr Author The series2 indeed only existed on disk1, and that disk was excluded. The help is not helpfull here, as far as I know the excluded only work when writing to the array, I did some searching on this before and found the following: Read the last part of this post... If this is indeed also valid for reads I have never completely understood how the system works.. I was under the impression that the user shares are just a representation of the main folders on all disk shares and that there was no further logic in there.. I thought that the excludes only worked together with split level and min free space to decide on what disk could be -written-.. Its that OR something got changed along the way at some point (because I have used the excluded before and have never noticed this.. with a lot of folders its hard to see..)
February 21, 20179 yr Global exclude was added as a way to safely navigate around the user share copy bug. If the disk is globally excluded from a user share, it's then safe to copy from that specific disk share to your user shares, and vice-versa, because the contents will not be duplicated in the user share system.
February 22, 20179 yr 1 hour ago, trurl said: Any disk which has files for the user share (top level folder) will be included for reads of the share, unless excluded globally from all user shares. which is another way of putting it.
Archived
This topic is now archived and is closed to further replies.