Wrong size of available space: UPDATE

ℹ️ Support
1

After upgrading from Nextcloud 11.0.3 to 12.0.0 the size of usable space of a user is not longer correct.
The user has 25 GB of space and when he opens he Web-Backend it’s shown “Sie verwenden 0 B von 10.1 GB (0 %)”, the same in the SyncApp.
2 of the directories-sizes are singed with"Ausstehend" (Pending).
It seems, that NC did not count the Size of these directories yet.

What is interesting: 10 GB can bee seen as free space and about 15 GB space is used by the User -> together 25 GB

Same problem in an different installation, same versions.

Is there any command to recount the size?

Any ideas?

Thanks

Chris

UPDATE: After deleting all the Files of der User, everything went fine…
Until i try to synchronize the files again. After the first Gb of files NC counts the size correctly. After about 8 GB it’s the same like after the Update. Size is “Pending” and it seems that NC counts “total size = grantes size - uploads” and the used size is “0”.

NC didn’t counts the size of files.

Any ideas??

2

I’ve the same issue.
Before update, with latest v11: 8GB quota, 6,3 used.
After update with v12: 0B used from 1,7GB.

Removed all files: 0 from 8 GB used. While uploading, the free space decreases.
Now, 5,8 of 6,3 GB uploaded, Web UI and Sync app shows: 0 of 4 GB used…

3

I have the same issue… Hope that there are no files lost?!
Any solution?

4

No solution available? Or are we the only ones with this problem?

Found a Issue in github that could be the same problem!

https://github.com/nextcloud/server/issues/5031

5

Correct. This seems to be the problem.

No solution so far??

6

Solution was found here: https://github.com/nextcloud/server/issues/5031

7

After upgrading from nextcloud 11.0.3 to 12.0.1 I can announce that this problem still persists.

8

Seeing the same here. For one user, 0 bytes is reported whereas the real space usage is somewhere around 120 GByte, for another, 825 MByte, while in reality some 120 Gbyte are used.

9

Obviously, we can expect a fix for NC 13: https://github.com/nextcloud/server/issues/6022

10

I can confirm that this has been fixed in the new NC 12.0.3 release.