copying a collection to provider with quota

[MontrealSergiy]

user may exceed file number quota by adding a sufficiently large collection to data provider (copy or move BAC)

[prioux]

That's by design, it's not a bug. We allow users to exceed their quota once, then we block the creation of new files afterwards. The reason is that it's much easier to get the state of "what is used NOW" and enforce the limit, than it is to check the state of "what it is NOW + what an operation will add". I'm closing the issue.

[MontrealSergiy]

Yet if quota reached you can not longer upload files, say if if quota is 0 then you can upload no file, quota 1 file you can upload one file ( as you suggested in #1529 (comment) ), but the second will be blocked.

I understand that it is for sake of code simplicity, but might confuse users.

I do not insist on fixing just wanted to document

[prioux]

I don't understand how users can be confused.

1. They can create files.
2. They can create files.
3. They can create files.
4. Oops, that last time they exceeded the quota, they can no longer create files.

If the quota is 0, it's even simpler:

1. They cannot create files.

What's confusing about all this?

[MontrealSergiy]

Perhaps another thing. When exceeded table shows

User	Data Provider	Max Size	Max Files	Usage
john	Storage	100 G	2302	Exceeded: Files (7.5 G and 2302 files)

Now users cannot upload more files, so yes, user should be warned. But I think the quota (2302) is not exactly exceeded but rather quota reached - or if you prefer quota fully used, utilized or met.