Hey 'folks,

 

We are currently trialing unRAID and migrating some data onto the box, but seem to be hitting issues with our cache drives. 

 

I have done some hunting around on the forums and cannot seem to find anything that matches our issue. 

 

Here is our array setup:

 

 

The only share we are -really- using at present is the Movies share, which is configured as follows:

 

(Note: Cache was set to "Yes" but this has been since changed to prefer, as moving umpteen odd terabytes was stalling as the cache was filling out before mover ran).

 

The Problem:

 

My cache drive is currently maxed out with only 200Mb free on there, Mover has been running now for about 12 hours and it has yet to move anything off that drive. 

 

I have tried to reboot the array, with no success and have also tried to remove the drives from the array, format and then re-insert but this problem keeps occurring.

 

I am 99.9% sure that this is me being an idiot and missing an obvious configuration setting somewhere, but I hope someone with more experience can shine a light on this? 

 

Recent SysLog:

 

Oct 20 09:39:03 unRAID shfs/user: cache disk full
Oct 20 09:39:03 unRAID shfs/user: cache disk full
Oct 20 09:39:03 unRAID root: rsync: write failed on "/mnt/cache/Movies/High Definition DTS/folder, film (2008)/[filmname].mkv": No space left on device (28)
Oct 20 09:39:03 unRAID root: rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]
Oct 20 09:39:03 unRAID move: file ./Movies/High Definition DTS/folder, film (2008)/[filmname].mkv rsync error: 11
Oct 20 09:39:03 unRAID root: .d..t...... ./
Oct 20 09:39:03 unRAID root: .d..t...... Movies/High Definition DTS/
Oct 20 09:39:03 unRAID root: .d..t...... Movies/High Definition DTS/folder, film (2008)/
Oct 20 09:39:03 unRAID root: >f+++++++++ Movies/High Definition DTS/folder, film (2008)/filmname).tbn
Oct 20 09:39:03 unRAID shfs/user: cache disk full
Oct 20 09:39:04 unRAID root: >f+++++++++ Movies/High Definition DTS/folder, film (2008)/FilmName-2008)-fanart.jpg
Oct 20 09:39:04 unRAID root: >f+++++++++ Movies/High Definition DTS/folder, film (2008)/Filmname- 2008)-trailer.mov
Oct 20 09:39:04 unRAID shfs/user: cache disk full
Oct 20 09:39:04 unRAID shfs/user: cache disk full
Oct 20 09:39:05 unRAID shfs/user: cache disk full
Oct 20 09:39:05 unRAID shfs/user: cache disk full
Oct 20 09:39:05 unRAID shfs/user: cache disk full

 

Change "Use cache disk" from "prefer" to "yes" and run the mover.

 

Thanks @Johnnie.black! Do you know if there is an easy way to kill the running mover so I can restart without bouncing the box?

Tom

IIRC on the console type:

 

mover stop

 

Thanks  @johnnie.black

 

This worked a treat at stopping the mover and I kicked off the job again...but so far nothing.

 

The syslog spits out the following when its running :

 

 

Oct 20 11:44:23 unRAID move: received signal 15, terminating!
Oct 20 11:44:23 unRAID shfs/user: cache disk full
Oct 20 11:44:23 unRAID shfs/user: cache disk full
Oct 20 11:44:23 unRAID root: rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(636) [sender=3.1.2]
Oct 20 11:44:23 unRAID root: rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(504) [generator=3.1.2]
Oct 20 11:44:23 unRAID move: file ./Movies/High Definition DTS/FilmName (2003)/FilmName-1080p-DTS- 2003).mkv rsync error: 20

[.....]

Oct 20 11:49:07 unRAID shfs/user: share cache full
Oct 20 11:49:07 unRAID shfs/user: share cache full
Oct 20 11:49:07 unRAID shfs/user: share cache full
Oct 20 11:49:07 unRAID shfs/user: share cache full
Oct 20 11:49:08 unRAID shfs/user: share cache full
Oct 20 11:49:08 unRAID shfs/user: share cache full
Oct 20 11:49:08 unRAID shfs/user: share cache full
Oct 20 11:49:08 unRAID shfs/user: share cache full
Oct 20 11:49:08 unRAID shfs/user: share cache full
Oct 20 11:49:08 unRAID shfs/user: share cache full
Oct 20 11:49:08 unRAID shfs/user: cache disk full
Oct 20 11:49:08 unRAID shfs/user: cache disk full
Oct 20 11:49:09 unRAID shfs/user: cache disk full
 

Did you change the use cache to "yes"? Or else you have another share wrongly set to "prefer".