I've found the problem and I have a fix in place now. An optimization for SD card access caused cached folders to be incorrect so it kept trying to recreate folders that were created during the sync processing, and when this occurs, instead of Google's storage access framework just using the existing folder, it creates a new folder with a "(1)" or "(2)" after it (depending on how many copies there are of the folder). I don't know why their library behaves this way. Thanks for helping me track this down.
Mike
Mike