Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Groupfolder quota greater 2 GB: Server replies Insufficent Storage. #98

Closed
RailsViceRoads opened this issue Mar 8, 2018 · 12 comments
Closed

Comments

@RailsViceRoads
Copy link

After applying a320c7f as recommended in #93 the quota for some group foloders can now be set greater than 2 GB. But although on the folders is sufficient storage space, the server sends "Insufficient Storage (Sabre\DAV\Exception\InsufficentStorage)" to the NC Sync client.

Server

  • NC 13.0.0.14
  • Group folders 1.2.0

Client

  • NC Client 2.3.3.1
  • Windows 10

Group Folder

  • Used 3 GB, Quota 10 GB

Behaviour: Folder was synced down to client without errors. After Some files was modified by user, the "Not-Synced"-list of client is containing all modified files with the error message "Insufficient Storage (Sabre\DAV\Exception\InsufficentStorage)". All other group folder with quotas less then 2 GB works as expected.

I have set the quota to "unlimited" now. I'll write a comment to this issue if sync now works for the user.

grafik

@RailsViceRoads
Copy link
Author

After I had set the quota to "unlimited" all clints synced her data without any additional user action. Looks like qota calculation can not handle quotas greater then 2 GB.

@fwmarcel
Copy link

Same Error

@kroerig
Copy link

kroerig commented May 16, 2018

Same error.

NC 13.0.2
Group Folders 1.2.0

Fileupload through browser.

@huste
Copy link

huste commented Nov 26, 2018

I can see the same wth 14.0.4 (I used 14.0.3 before where it started happening). I have set my users and group folder to 50GB; admittedly, I increased the grouop folder quota to 50 only a few days ago. I was getting the same errors as RailViceRoads posted in his screenshot. Plus on another client which also tried uploading files with another non-admin client gave me "Das Hochladen überschreitet das Speicherkontingent" (roughly: uploading fails due to exceeded quota). And that's after setting quotas to unlimited for the users and the shared folder and closing and restarting the client. Pressing "retry uploads" seems to now upload at least most of the files, while still nagging about others ("due to previous errors", as it states).
[...]
After restarting again, all files went into the cloud.

NextCloud 14.0.4
Group Folders 1.3.3

@icewind1991
Copy link
Member

Do you have a 32bit php version?

@huste
Copy link

huste commented Nov 27, 2018

Must be 32bit, since echo PHP_INT_SIZE returns 4. Is there a more elgant way to check which php Nextcloud is actually using?

@ZeikoFr
Copy link

ZeikoFr commented Dec 3, 2020

Hi @RailsViceRoads is the issue still relevant ?

@RailsViceRoads
Copy link
Author

Hi @RailsViceRoads is the issue still relevant ?

Today I have still all large group folders set to "unlimited". I'll check if the issue still exist next days.

@ZeikoFr
Copy link

ZeikoFr commented Dec 3, 2020

Today I have still all large group folders set to "unlimited". I'll check if the issue still exist next days.

Thanks, I tried with my NC 19 and NC 20 instance and I could not replicate this issue on my end, if you encounter the issue please post more information about your actual environnement

@RailsViceRoads
Copy link
Author

I have set all large group folders from "unlimited" to 8 or 16 GB at sunday. Till now I received no error reports from my users. I'll give you a final report end of the week.

By the way. Since I opened the issue I changed a lot:

  • NC 20.0.2
  • host changed from 32 to 64 bit system
  • actual PHP version is now 7.4

Since host change, an other issue (nextcloud/server#13160) is vanished without a trace. Could it be, that the integer representation has changed by change the system?

@RailsViceRoads
Copy link
Author

Today still no error reports from users. For my NC-instance the error seems to be gone away.
@ZeikoFr I have no chance to check this on the old 32 bit system. So for me the issue is not longer relevant.

@ZeikoFr
Copy link

ZeikoFr commented Dec 15, 2020

Thanks @RailsViceRoads if it seems ok for you I let you close the issue, you can always open it again in case you get the same problem in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants