Greetings,

 

I recently purchased and installed unRaid 6.2.4 onto my server.  After transferring all of my media to the data array I enabled a parity disk and changed the media share setting to "Prefer" for the cache.  My assumption is that anything in the future will first be saved to the cache and then moved per the schedule to the array.  For whatever reason the mover has now filled up my cache drive with data from my array and I am now worried that it is destroying data that can not be moved?  I am not sure if i should do a forced reboot or wait for the mover process to end.  I tried killing the mover process but it did not stop.

 

Why is this happening?  I thought the purpose of the cache is for performance and data should be moved to the array by the mover, not the other way around.  What am I doing wrong?

 

Below is a snippet of my running log:

 

ErrorWarningSystemArrayLogin

 

 

Jan 24 09:10:39 unRaid root: >f+++++++++ Media/Plex/TV Shows/The Men Who Built America/series.xml

Jan 24 09:10:39 unRaid shfs/user0: err: shfs_rmdir: rmdir: /mnt/disk1/Media/Plex/TV Shows/The Men Who Built America (39) Directory not empty

Jan 24 09:10:39 unRaid move: rmdir: /mnt/user0/./Media/Plex/TV Shows/The Men Who Built America Directory not empty

Jan 24 09:10:39 unRaid shfs/user: cache disk full

Jan 24 09:10:39 unRaid root: cd+++++++++ Media/Plex/TV Shows/Scorpion/

Jan 24 09:10:39 unRaid root: cd+++++++++ Media/Plex/TV Shows/Scorpion/Season 03/

Jan 24 09:10:39 unRaid root: >f+++++++++ Media/Plex/TV Shows/Scorpion/Season 03/S03E06 - Bat Poop Crazy.mkv

Jan 24 09:10:43 unRaid shfs/user: cache disk full

Jan 24 09:10:48 unRaid shfs/user: cache disk full

Jan 24 09:10:48 unRaid root: rsync: write failed on "/mnt/cache/Media/Plex/TV Shows/Scorpion/Season 03/S03E06 - Bat Poop Crazy.mkv": No space left on device (28)

Jan 24 09:10:48 unRaid root: rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]

Jan 24 09:10:48 unRaid move: rsync error: 11

Jan 24 09:10:48 unRaid root: .d..t...... Media/Plex/TV Shows/

Jan 24 09:10:48 unRaid root: .d..t...... Media/Plex/TV Shows/Scorpion/

Jan 24 09:10:48 unRaid root: .d..t...... Media/Plex/TV Shows/Scorpion/Season 03/

Jan 24 09:10:48 unRaid root: >f+++++++++ Media/Plex/TV Shows/Scorpion/Season 03/S03E05 - Plight at the Museum.mkv

Jan 24 09:10:52 unRaid shfs/user: cache disk full

Jan 24 09:10:56 unRaid shfs/user: cache disk full

Jan 24 09:10:56 unRaid root: rsync: write failed on "/mnt/cache/Media/Plex/TV Shows/Scorpion/Season 03/S03E05 - Plight at the Museum.mkv": No space left on device (28)

Jan 24 09:10:56 unRaid root: rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]

Jan 24 09:10:56 unRaid move: rsync error: 11

Jan 24 09:10:57 unRaid root: .d..t...... Media/Plex/TV Shows/Scorpion/Season 03/

Jan 24 09:10:57 unRaid root: >f+++++++++ Media/Plex/TV Shows/Scorpion/Season 03/S03E08 - Sly and the Family Stone.mkv

Jan 24 09:10:59 unRaid shfs/user: err: shfs_write: write: (28) No space left on device

Jan 24 09:10:59 unRaid shfs/user: err: shfs_write: write: (28) No space left on device

Jan 24 09:11:00 unRaid shfs/user: err: shfs_write: write: (28) No space left on device

Jan 24 09:11:00 unRaid shfs/user: cache disk full

Jan 24 09:11:04 unRaid shfs/user: err: shfs_write: write: (28) No space left on device

Jan 24 09:11:04 unRaid shfs/user: err: shfs_write: write: (28) No space left on device

Jan 24 09:11:04 unRaid shfs/user: cache disk full

Jan 24 09:11:08 unRaid shfs/user: err: shfs_write: write: (28) No space left on device

Jan 24 09:11:08 unRaid shfs/user: err: shfs_write: write: (28) No space left on device

Jan 24 09:11:09 unRaid root: rsync: write failed on "/mnt/cache/Media/Plex/TV Shows

Enable help in the GUI and read the description of the cache options. Cache prefer is used to designate the cache drive as the preferred final destination of the data. You want cache: yes.

Thanks... What is the recommended path for me now? Do I let the mover continue to run (I assume it will eventually stop on its own)? Or do I change the setting to yes and reboot?  I assume the mover will them put the files back to the cache.

 

Thank you!

Honestly I don't know. This has come up before, and there doesn't seem to be a good way to get the mover to stop when it's in this state. If it were me, I'd change the setting to yes, and see if the mover eventually gives up so you can reboot cleanly.

Trying to abort the Mover can be a bit messy. See here. It might be worth letting it just run its course. Once you've changed the setting to "Yes" the files will be moved back to the array the next time the Mover runs. The default is overnight but you can change that or run it manually, as you wish. No need to reboot but doing so would get rid of those "cache disk full" messages in your syslog.

 

Trying to abort the Mover can be a bit messy. See here. It might be worth letting it just run its course. Once you've changed the setting to "Yes" the files will be moved back to the array the next time the Mover runs. The default is overnight but you can change that or run it manually, as you wish. No need to reboot but doing so would get rid of those "cache disk full" messages in your syslog.

My personal preference would be to reboot to a clean state after the mover is done, much easier to troubleshoot any more issues that may come up. Wading through a bunch of garbage in a syslog can be tedious.

Trying to abort the Mover can be a bit messy. See here. It might be worth letting it just run its course. Once you've changed the setting to "Yes" the files will be moved back to the array the next time the Mover runs. The default is overnight but you can change that or run it manually, as you wish. No need to reboot but doing so would get rid of those "cache disk full" messages in your syslog.

My personal preference would be to reboot to a clean state after the mover is done, much easier to troubleshoot any more issues that may come up. Wading through a bunch of garbage in a syslog can be tedious.

And if syslog gets too full it will run out of room.

Thanks for all the input guys.. I guess I will let it run its course and reboot and manually invoke the mover again to move my data back.