Neardood

I created a share, then after doing so set all of the avaliable discs to excluded. After this I mapped it as a network drive. The drive showed the total free space of the array, but when I went to write a file to it from windows, I got the error message "there is not enough space on [share name]". The kind folks on reddit pointed out that I had in fact had all drives excluded, and after including them all this fixed the issue. The SMB system should not show a drive with free space if there are no allowed discs in unraid. Someone actually tested this; here is their findings: "When I tried to add a share, and excluded all my disks (with or without cache), the share would not create, instead of showing a share with 0 bytes free. Thinking about this, it's normal: a share is just a folder in /mnt/user/[sharename], and if it can't write to any array disk, it can't make that folder. Now the weird part: If the share is already created (ie, the share folder exists on disk1 in my case), and you exclude all disks, it will still show the free space of disk1. If I now create the same folder on disk2, it still only shows the free space of disk1. If I remove disk2 from excluded disks (so disk1 is excluded with the folder, disk2 is not excluded with the folder), it will show the free space on disk1+disk2. This is clearly a bug: As soon as the share can be created (not all disks excluded), the free space column will always show the free space of the first disk containing the folder (even if excluded), plus the free space of included disks, while it should only show the free space of included disks."