Sorry to hear you’re facing problems
In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:
Or for longer, use three backticks above and below the code snippet:
longer example here
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can
Nextcloud version (eg, 12.0.2): 17
Operating system and version (eg, Ubuntu 17.04): Debian 10
Apache or nginx version (eg, Apache 2.4.25): nginx
PHP version (eg, 7.1): 7.3.11
The issue you are facing:
(edited for clarity)
I have problems with my following setup:
- Admin user who owns all the data and has a big quota.
Example folders would be:
- “Pictures” with subfolders:
- “Clorge Jooney”
- another top-level folder “Videoclips” with subfolders:
- “Short clips”
- “Clorge Jooney”.
- “Pictures” with subfolders:
- Some “single” users, let’s call one of them User A.
- Admin shares with User A:
- “Videoclips/Clorge Jooney”
- User A now sees two folders:
- “Pictures” with subfolders “Clorge Jooney” and “Cars” within it
- and on the same hierarchy level as “Pictures”, he sees “Clorge Jooney” from the single shared subfolder of the “Videoclips” section.
- Now User A gets confused and wants to tell the “Clorge Jooney” videoclips folder (which he sees right in his top-level directory) apart from the “Clorge Jooney” folder inside his “Pictures” folder. So he renames his top-level Clorge Jooney folder into “Clorge_clips”.
As far as I know, since everything that was shared with User A belongs to the Admin user, User A should be able to create stuff inside those folders etc., and everything would count towards the quota of the Admin. As stated here: https://docs.nextcloud.com/server/latest/user_manual/files/quota.html
Now what I CANNOT understand is: After User A has renamed the folder on his end, it seems like the renamed folder’s size starts counting against User A’s quota. I have no way to check the “contents” of User A’s quota (at least none that I am aware of), but as soon as User A renames something and his desktop client performs a synchronization, User A’s quota starts to fill up.
Why is this? I thought the shared folders could be named as the users want them to name, because NC identifies them via some sort of database id anyway, and therefore it did not matter which names the users would give to their folders?
(I did this setup to prevent my Users to eat so much quota individually that my server would be out of space.)
Please help! How can I resolve this? What I would like is the setup as described above, but with the Users being able to name the folders as they prefer.
Greetings to all!
Is this the first time you’ve seen this error? (Y/N): Y
Steps to replicate it:
- see above
The output of your Nextcloud log in Admin > Logging:
The output of your config.php file in
/path/to/nextcloud (make sure you remove any identifiable information!):
The output of your Apache/nginx/system log in