Two things i do not get: - Why can't Google figure out what the conditions which trigger this issue are and add a caveat to the documentation? "Bad things will happen if you use more than 500,000 files on a 32 bit client." This would save both their support organization and their customers a lot of pain. - Why does this particular user not give up on Google Drive if it does not work for him, or at least try to figure…
You can't fix software breakage by adding mentions in random documentation pages.
Bad things shouldn't happen if you have more than 500,000 files. And if such things are unavoidable due to limits that are out of Google's control, like from the operating system or the CPU architecture, then the software should warn the user well in advance before any damage occurs.
Google has all the manpower it needs. But this is again one of those instances where they show how little they care. Which should have been obvious by now, given that with all of their manpower and virtually unlimited resources, they still haven't released a Linux client.
This is why I'm staying on Dropbox btw. My data is too important for me to entrust a company that will sell cloud storage as a complementary to something else.