Owncloud: 8.2.1 (stable)
System: Debian 7.9
'memcache.local' => '\\OC\\Memcache\\Redis',
'memcache.locking' => '\\OC\\Memcache\\Redis',
'host' => '/var/run/redis/redis.sock',
'port' => 0,
'timeout' => 0,
'theme' => '',
'maintenance' => true,
'asset-pipeline.enabled' => true,
'log_rotate_size' => 104857600,
What I did:
A user had no space left on his account, so he moved a bigger file (1GB) to a folder shared by another user though the web interface.
Now the file should not count against that user's quota anyumore and he should be able to upload new files.
The 1 GB still counted against the users quota and he was not able to upload new files.
Manually triggering a rescan through the occ console command fixed the wrong space usage calculation. The user can now upload new files.
@Bubu we need your ownCloud version
@icewind1991 size propagation issue maybe ?
Sorry, the OC Version must have been lost to copy&paste. updated the post: v8.2.1 (stable)
I did a few more tests. Suppose we have the following Structure of files:
File1 gets moved to Shared_Folder.
Still happening on v8.2.5.
It looks like cross-storage move isn't triggering a size update in the database.
@icewind1991 potential regression.
This works properly in 9.0.2, possibly because etag + size propagation has been rewritten in a different way.
Also broken in 8.0.8 v8.1.8
Works fine in v8.0.13.
Initiating bisect sequence
So, I did a bisect and only observed the Webdav property "quota-available-bytes".
Before this commit d7b3a1a, moving a file into a received share would properly update the "quota-available-bytes" value. After this commit, the value stays unchanged.
However I also observed that the other property "quota-used-bytes" was not always updated, so this will need another bisect...
Okay, regarding "quota-used-bytes" it's another topic. It might be a valid value and includes the size of files used in received shared folders. So it might be correct.
I'll check the oc_filecache entries instead.
Bisect result: after the same commit d7b3a1a doesn't properly update the size of the "files" entry in the database after doing a cross-storage move.
For OC < 9.0 any unexplained insufficient space issue could be related to this one.
Fix is here #25101