I have a user share created called "TV Shows" and within that are folders for each show ("Cheers", "Seinfeld", etc.).  Whenever I write to one of the folders ("Dexter"), I get an error stating there's not enough space.  The funny thing is that writing to other folders within that same user share do not report this and take whatever I copy over to them.  The server has over 600 GB of free space and the "TV Shows" user share is not restricted to any specific disks.  I am stumped and would appreciate it if someone could shed some light on this.  Below are a couple screen shots showing the available space and the set up of the user share.

 

 

 

 

Also, the syslog shows nothing at all.

I have a user share created called "TV Shows" and within that are folders for each show ("Cheers", "Seinfeld", etc.).  Whenever I write to one of the folders ("Dexter"), I get an error stating there's not enough space.  The funny thing is that writing to other folders within that same user share do not report this and take whatever I copy over to them.  The server has over 600 GB of free space and the "TV Shows" user share is not restricted to any specific disks.  I am stumped and would appreciate it if someone could shed some light on this.  Below are a couple screen shots showing the available space and the set up of the user share.

 

 

 

 

Your split level is set to "1"  That will allow the "TV Shows" folder to be automatically created, if needed on the various drive, but it indicates that for any folder under that level, all files must reside on the same disk as the existing folder.

 

So, for each of your directories with specific show, the disk it is on initially must hold it all.

 

I'll be the one show you have problems with is on disk1.  It has very little free space and you've configured your server to not allow it to use the other disks.

You probably want to set your split level to "2" and that way the "Dexter" folder can be split across more than one physical disk.  (Dexter is level 2, "TV Shows" is level 1)

 

Joe L.

That was pretty stupid of me to overlook that, but that still doesn't fix the problem.  I tried setting it to 2 and I still get 'not enough space'. 

I had a similar problem with mover not moving from my cache drive to the protected array.  Syslog said out of disk space but the array had plenty of capacity and I am using user shares.  I increased my split level from 2 to 3 but it did not fix the issue.  I read elsewhere in this forum that setting the highwater split level to 99 worked for others.  I tried it and all is good.  You probably just need to keep increasing the split level until the directory structures are in line with your split level threshold.  If you get tired of figuring that out just go to 99 and you should be covered.

 

A warning to others using user shares and a cache drive -- I was under the false impression that my data was protected in the array.  Actually, because of split levels my data was not being moved off of the cache drive at night.  I didn't figure it out for months until I saw from the dashboard that my cache drive was filling up.  Then I looked at the syslog and saw all the error messages. 

 

If you use the cache drive and mover please check periodically that the drive has actually moved your data into the array and not just errored out.  I might try to add a loop for this in unRAID Notify which emails the status of the array.  Would be nice to get an email if mover had errors I should know about.  Good Luck.

I finally got some time to look into this some more, and Joe L. was right.  It had started writing the file to disk1.  Once I changed split level to 2 and deleted the portion of the file on disk1, it copied over fine.  Thanks for the help.