To add insult to injury the new sync client (backup&sync I believe it is called) is a disaster in two ways: I opened a thread at the time with what you can and can't do to share experiences with GFS after discovering that little works beside copying some files from here to there and streaming some video files, one at a time (I've been more interested in using it for portable apps, heck no even for very small ones). Solution is to wait until the delete is complete before renaming.
This causes broken content (I had a LOT of them). "B.doc" rename to "A.doc") 3) GDFS will attempt to download B.doc before renaming it, but at the same time, upload this unfinished B.doc as A.doc back to GDFS. "A.doc") 2) rename another file to the deleted file name (i.e.
GDFS attempts to distinguish them with (1), (2) suffix.Īnother problem I came across is that if you perform a few operations in sequence (in this particular sequence):ĭelete a file (i.e. This creates issues for many sync clients, including ExpanDrive, MountainDuck, etc. test.doc and test.doc under G:\My Drive\My Documents. For example, google drive allows files / folders of the EXACT same name to be placed in the same location. First of all I had to say that if you use GDFS it is really, really good at streaming downloads but not so much uploads.Īs for file naming there is a slight discrepancy on how it displays them in explorer vs the actual file system on Google Drive.
0 kommentar(er)
