Hi,

 

I am looking for some advice Re: mover script and files being left behind on the cache drive after the mover is successful. I have searched the Forums and it does not seem to be an Extended Attributes problem (see attached syslog.txt), and suspect it may be an issue with long filenames but would like someone with more knowledge of unRAID to take a look.

 

First a bit of background.

 

I currently run unRAID 5.0 Plus, with a cache drive containing all my Appdata on a cache only share.

I recently made some changes to my Plex Library setup, so decided to backup in case anything got broken in the process. I logged in via Putty and used mc to Copy the contents of my /mnt/cache/Appdata to /mnt/user/Backup/unRAID/Appdata, which appeared to go successfully.

Following the successful update of my Plex Library I decided to rename my first backup in the Backup folder to plex_old and re-copy plex over. I though everything worked fine until I decided to manually run the Mover script & the Mover took approx. 8 hours to complete. Initially I was a bit worried, but thought that adding plex_old and plex (each around 7Gb of small Library files) may take some time to add to the array with parity etc.

 

Okay, onto my problem:

Now, following the sucessful completion of the mover I still have a Backup folder on my Cache drive with Plex files which should have been copied to the array and deleted (specifically /mnt/cache/Backup/unRAID/Appdata/plex/Library/Application Support/Plex Media Server/Metadata/ and /mnt/cache/Backup/unRAID/Appdata/plex_old/Library/Application Support/Plex Media Server/Metadata/ and their contents).

 

I have attached a copy of my syslog.txt to this post.

Could someone please advise me whether this is in fact a long filename issue or what steps to take to check that the Backup has completed (how to check source and destination maybe).

 

Thanks in advance

syslog.txt

Would it be worth trying to copy the contents of my Appdata folder directly to a disk rather than a user share?

 

This would lead to a shorter path/filename (/mnt/disk1/Appdata as opposed to /mnt/user/Backup/unRAID/Appdata) and may fix my problem if it is a filename length issue. If I am to try this the Backup data would not be protected by Parity seeing that it is not included in a User share is that correct? (unless I copy to multiple disks of course)