I've got several reports like this in my log file:

Feb 15 03:40:01 NAS logger: mover started

Feb 15 03:40:01 NAS logger: moving Home Movies/

Feb 15 03:40:01 NAS logger: ./Home Movies/School/2014-15/2015.02.17 ISSMA Solo & Ensemble/Ian Quartet.mp4

Feb 15 03:40:01 NAS logger: .d..t...... ./

Feb 15 03:40:01 NAS logger: >f.stpog... Home Movies/School/2014-15/2015.02.17 ISSMA Solo & Ensemble/Ian Quartet.mp4

Feb 15 03:40:36 NAS shfs/user0: shfs_write: write: (28) No space left on device

Feb 15 03:40:36 NAS logger: rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) (Minor Issues)

Feb 15 03:40:36 NAS logger: rsync: write failed on "/mnt/user0/Home Movies/School/2014-15/2015.02.17 ISSMA Solo & Ensemble/Ian Quartet.mp4": No space left on device (28) (Minor Issues)

Feb 15 03:40:36 NAS logger: rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7] (Errors)

Feb 15 03:40:36 NAS logger: rsync: connection unexpectedly closed (31 bytes received so far) [sender]

 

Why would the mover be attempting to put files on a disk without enough space? Attached is a screen shot of the share setup, and there is currently 4.3TB of space available to the share.

What values have you specified for the 'split level', 'include disks'/'exclude disks' and 'allocation method' for the 'Home Movies' share as these control where new files will be written?

 

Why would the mover be attempting to put files on a disk without enough space? Attached is a screen shot of the share setup, and there is currently 4.3TB of space available to the share.

I think that your problem may be the fact that you have the "Fillup" Allocation method specified together with a 0 value for the In Free Space.    I think if you set the "Min Free Space" to at least the size of the largest file you want to copy then it will work OK.

 

The rational for this is that unRAID selects a disk for creating a new file based on an initial size of zero (which is what it is when it is initially created).  It then starts writing that file and if there is not enough space on the selected disk will end up giving a write error due to lack of space.  Setting the Min Free Space to the at least the size of the Largest file means this scenario will never happen as a file would always be able to be completely written once started without running out of space.

 

You might well also be able to avoid the issue by selecting a different allocation method, but I assume that you have deliberately chosen the Fillup method (as that is not the default).

I think that your problem may be the fact that you have the "Fillup" Allocation method specified together with a 0 value for the In Free Space.    I think if you set the "Min Free Space" to at least the size of the largest file you want to copy then it will work OK.

 

You might well also be able to avoid the issue by selecting a different allocation method, but I assume that you have deliberately chosen the Fillup method (as that is not the default).

 

I chose this because they are generally small video clips from the cell phone, and I was hoping to fill in smaller gaps on disks with minimal space. Guess I chose wrong. That, combined with the fact that a short video from the cell phone (at 1920x1080) is 1GB + doesn't really make it 'small'.

 

I've increased the minimum size to 1GB, and I will probably switch fill methods, as well.

 

I'll report back when the mover's had a chance to run, to see if it's worked OK.

 

Thanks!

I chose this because they are generally small video clips from the cell phone, and I was hoping to fill in smaller gaps on disks with minimal space. Guess I chose wrong. That, combined with the fact that a short video from the cell phone (at 1920x1080) is 1GB + doesn't really make it 'small'.

If you really want to fill up a disk you can move files to the disk level shares rather than the user shares.  Doing it that way explicitly selects the drive so unRAID ignores the User Share settings.

 

Also on modern disks, 1GB is a very small proportion of the total disk space!