Jump to content
Covecube Inc.
  • 1
KiLLeRRaT

Google Drive: The limit for this folder's number of children (files and folders) has been exceeded

Question

Hi All,

I've recently noticed that my drive has 40GB to be uploaded, and saw there are errors in the top left.  Clicking that showed 

Quote

The limit for this folder's number of children (files and folders) has been exceeded

What's the deal here, and is this going to be an ongoing issue with growing drives?

My drive is a 15TB drive, with 6TB free (so only using 9TB).

Attached is my drive's info screen.

EDIT: Cloud Drive Version: 1.1.5.1249 on Windows Server 2016.

 

Cheers,

2020-06-18 11_42_07-mRemoteNG - confCons.xml - oscar.gouws.org.png

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0
On 10/9/2020 at 5:28 PM, JoeyD said:

Managed to fix this today as my client was giving errors also. 

Install Beta version from here: http://dl.covecube.com/CloudDriveWindows/beta/download/ (I used 1344)

Reboot.

Don't start CloudDrive and/or service.

Add the below to this file: C:\ProgramData\StableBit CloudDrive\Service\Settings.json

   "GoogleDrive_ForceUpgradeChunkOrganization": {
    "Default": true,
    "Override": true
  } 

Start Service & CloudDrive. Should kick in straight away. I have 42TB in GDrive and it went through immediately. Back to uploading as usual now. 

Hope this helps. 

After seeing the positive feedback from other people, I downloaded the beta and applied the settings by JoeyD. Can confirm this works! Thanks @JoeyD! :)

Share this post


Link to post
Share on other sites
  • 0

Get ready to lose the "unlimited" GDrive storage. The new Workspace TOS spell out that beyond 5TB per Enterprise user it will remain within Google's discretion to grant you extra storage.

I just got the email introducing the new plans, I'm guessing that we have a few months left before they force the transition, a year at best for those people who just signed up to an annual GSuite plan before they were retired. I just checked and it doesn't look like you can convert a flexible (i.e. monthly) plan to an annual Gsuite plan, now it's all about migrating us to Workspace.

Share this post


Link to post
Share on other sites
  • 0
3 hours ago, Gijs said:

After seeing the positive feedback from other people, I downloaded the beta and applied the settings by JoeyD. Can confirm this works! Thanks @JoeyD! :)

There should be no reason to change any advanced settings, and I would discourage people from doing so unless you specifically need to change those settings for some reason. The per-folder limitation issue should be resolved by using a beta newer than .1314 with the default settings.

Share this post


Link to post
Share on other sites
  • 0
3 hours ago, otravers said:

I just got the email introducing the new plans, I'm guessing that we have a few months left before they force the transition, a year at best for those people who just signed up to an annual GSuite plan before they were retired. I just checked and it doesn't look like you can convert a flexible (i.e. monthly) plan to an annual Gsuite plan, now it's all about migrating us to Workspace.

Several people have confirmed that the "Enterprise Standard Plan" is $20 a month and retains the unlimited with even a single user. So this isn't likely to translate to much more than a price increase.

See, for an example: https://old.reddit.com/r/DataHoarder/comments/j61wcg/g_suite_becomes_google_workspace_12month/g7wfre3/

Share this post


Link to post
Share on other sites
  • 0
On 10/9/2020 at 11:28 AM, JoeyD said:

Managed to fix this today as my client was giving errors also. 

Install Beta version from here: http://dl.covecube.com/CloudDriveWindows/beta/download/ (I used 1344)

Reboot.

Don't start CloudDrive and/or service.

Add the below to this file: C:\ProgramData\StableBit CloudDrive\Service\Settings.json

   "GoogleDrive_ForceUpgradeChunkOrganization": {
    "Default": true,
    "Override": true
  } 

Start Service & CloudDrive. Should kick in straight away. I have 42TB in GDrive and it went through immediately. Back to uploading as usual now. 

Hope this helps. 

THIS WORKS! THANK YOU SO MUCH!

Share this post


Link to post
Share on other sites
  • 0
On 10/12/2020 at 9:38 AM, Gijs said:

Managed to fix this today as my client was giving errors also. 

Install Beta version from here: http://dl.covecube.com/CloudDriveWindows/beta/download/ (I used 1344)

Reboot.

Don't start CloudDrive and/or service.

Add the below to this file: C:\ProgramData\StableBit CloudDrive\Service\Settings.json

   "GoogleDrive_ForceUpgradeChunkOrganization": {
    "Default": true,
    "Override": true
  } 

Start Service & CloudDrive. Should kick in straight away. I have 42TB in GDrive and it went through immediately. Back to uploading as usual now. 

Hope this helps. 

I did the following but i keep getting drive cannot be mounted please help.

error.JPG

Share this post


Link to post
Share on other sites
  • 0
9 hours ago, CMBC said:

All my ReFS drive are now RAW, lost everything....

 

6 hours ago, havok said:

I did the following but i keep getting drive cannot be mounted please help.

Neither of these errors/issues are likely related to the topic of this thread.

If the drive is RAW, the file system is likely corrupted. The change this thread references only restructures the way the data is stored on the provider, it isn't changing any of the data itself. If it was corrupting data on the provider, we'd be seeing that manifest in other ways for other users--and that isn't the case. I would suggest opening a ticket with support here: https://stablebit.com/Contact in order to try and troubleshoot how your file system was actually corrupted. Though even Windows Updates have corrupted ReFS volumes on a regular basis. It just isn't a stable file system, and that's why the functionality has been rolled back in Windows 10 for now. So if you blinked or breathed wrong, that might be the culprit.

And a User Rate Limit Exceeded error is an API limit error. It means the API key you're using is hitting the limit of calls per time period, and Google won't allow it to access the API any more. Are you using the default API key, or your own?

 

 

Share this post


Link to post
Share on other sites
  • 0
On 10/15/2020 at 2:13 AM, srcrist said:

Hello, just try yourself, easy to verify.

Using beta 1.2.0.1346, create an REFS drive on Google, after formating, remove drive letter, it goes RAW...

 

On 10/15/2020 at 2:13 AM, srcrist said:

Neither of these errors/issues are likely related to the topic of this thread.

If the drive is RAW, the file system is likely corrupted. The change this thread references only restructures the way the data is stored on the provider, it isn't changing any of the data itself. If it was corrupting data on the provider, we'd be seeing that manifest in other ways for other users--and that isn't the case. I would suggest opening a ticket with support here: https://stablebit.com/Contact in order to try and troubleshoot how your file system was actually corrupted. Though even Windows Updates have corrupted ReFS volumes on a regular basis. It just isn't a stable file system, and that's why the functionality has been rolled back in Windows 10 for now. So if you blinked or breathed wrong, that might be the culprit.

And a User Rate Limit Exceeded error is an API limit error. It means the API key you're using is hitting the limit of calls per time period, and Google won't allow it to access the API any more. Are you using the default API key, or your own?

 

 

 

Share this post


Link to post
Share on other sites
  • 0
12 hours ago, CMBCBE said:

Using beta 1.2.0.1346, create an REFS drive on Google, after formating, remove drive letter, it goes RAW...

Open a ticket using the link provided in the post you quoted. They'll get you sorted.

Share this post


Link to post
Share on other sites
  • 0

Hello I'm experiencing the same error as "The limit for this folder's number of children (files and folders) has been exceeded" so I switched to the latest stable version of CloudDrive now I get errors only for 1 disk while before I received errors for all my disks (5 disks) I noticed when uploading to the disk that gives me error 2.22 GB is it possible that the upload refers to the structural change of the disk? I don't remember uploading anything on that disk, do you think you need to go to the beta and force the system by manually editing the file to solve it?
I have read that some users have found the disk unusable, even if experienced users like srcrist do not associate this error with the change, I would like to totally avoid finding myself in this situation. Thanks to anyone who wants to help me

Share this post


Link to post
Share on other sites
  • 0

Is there any work pending on fixing GDrive issue? Any estimate?

I'm just not ready to risk a beta version of software and lose again TBs of data as it happen in the past.

Share this post


Link to post
Share on other sites
  • 0

I am also haviing the same issue after the upgrade. 

error.JPG

 

Pretty sure the drive was NOT REFS as its connected to a Windows 7/Windows Embeded Standard x64 system. 

I DID NOT apply the code below that will be my next step

Add the below to this file: C:\ProgramData\StableBit CloudDrive\Service\Settings.json

   "GoogleDrive_ForceUpgradeChunkOrganization": {
    "Default": true,
    "Override": true
  } 

 

 

I used BETA version 1346 incase that helps anyone. 

Share this post


Link to post
Share on other sites
  • 0
21 hours ago, Krisp said:

Is there any work pending on fixing GDrive issue? Any estimate?

The fix for these issues is several months old. It was fixed back in July.

21 hours ago, Krisp said:

I'm just not ready to risk a beta version of software and lose again TBs of data as it happen in the past.

.1318 is the latest stable release on the site, and it has the fix (which was in .1314). You don't need to use a beta version, if you don't want.

Share this post


Link to post
Share on other sites
  • 0
2 hours ago, TMGPhilip said:

I am also haviing the same issue after the upgrade. 

User Rate Limit Exceeded is an API congestion error from Google. If you're being given that error, and you're using your own key, you're hitting the usage limits on your key. If you're using Stablebit's default key, then they are hitting their limits--which is possible, especially if many people are having to do a lot of API calls at once to convert drives. That's just speculation, though.

If it's stablebit's key, you'll want to open a ticket and let them know so they can request a raise on their limit. You can also try reauthorizing the drive, as stablebit has several API keys already--or switching to your own.

Share this post


Link to post
Share on other sites
  • 0
4 minutes ago, TMGPhilip said:

i just had to wait a few hours and it cleared itself. Is there any clear documentation on using our own api key? 

Yessir. This article on the wiki details the process: https://wiki.covecube.com/StableBit_CloudDrive_Q7941147

Note both that the process on Google's end is a little outdated (though you can still probably navigate the process from that article), and that switching to a personal key isn't really necessary and carries new limitations relative to Stablebit's developer keys (for example, people using their personal keys were already getting these per-folder limitations back in June, while Stablebit's key has just had this limitation enforced this month). So, caveat emptor.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...