ressu 13 Posted December 19, 2015 Posted December 19, 2015 A while back, I ran into a problem with my Google Drive sync. Emby left the leftover files from sync to the drive. Initially I assumed that the issue was in my drive (I had 2 data.json files in the sync folder for some reason) and I deleted all synced files. After a while, the situation reoccurred. "No problem, the Google drive sync has a bug in it", I thought and moved to a local sync folder. For a while things worked fine (granted, I didn't have time to look after the sync folder), but now I noticed that the same issue is repeating in the local sync folder. My sync jobs have "sync unwatched videos only" set, so things get removed from sync queue. But for some reason the files are still present on the sync destination afterwards. The issue has persisted for quite some while, but I'm currently running version 3.0.5781.5, after a brief search I was unable to find anything relevant in the logs, so if there is something that is needed for debugging, I'll gladly look it up. I just couldn't find anything for now.
Luke 42083 Posted December 19, 2015 Posted December 19, 2015 Thanks, I found the issue. The fix wont' be able to cleanup files that should have been deleted before, because it thinks they already are. But it will be resolved going forward.
ressu 13 Posted December 19, 2015 Author Posted December 19, 2015 Awesome. Is there a way to easily clean up the extra files or should I just wipe them all and allow the sync to recreate them (once the fix is in place that is)?
Luke 42083 Posted December 20, 2015 Posted December 20, 2015 you don't need to wipe files that are currently in the synced state. the ones you need to wipe are the ones that were supposed to be removed, because the sync process thinks they have already been successfully removed.
ressu 13 Posted December 21, 2015 Author Posted December 21, 2015 Yeah.. that's what I figured. But it's going to be a tough call to find all files that should have already been deleted. I have 4 sync jobs which push data to that destination, so there are a lot of files that should be there as well as files that should be removed. It's just easier to remove them all. But hey, that's just work for the CPU, not me
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now