through the web-ui:
on win7 desktop with client v2.2.4.2:
Moving content from one share to another should work smoothly
The following inconsistency has appeared on the server: through the web-ui UserB can see the BAR folder inexplicably duplicated.
If FolderA and FolderB is shared with several other users working on them, users keep getting the "Backup Detected" dialog asking wether to keep conflict files or to synchronize normally.
https://help.nextcloud.com/t/duplicate-files-delete-not-possible/8869/7
https://github.com/nextcloud/server/issues/741
Operating system:
Ubuntu 16.04
Web server:
Apache 2.4
Database:
Mysql 5.7
PHP version:
v5.6
Nextcloud version: (see Nextcloud admin page)
v10.0.3
Updated from an older Nextcloud/ownCloud or fresh install:
updated from 10.0.0 -> ... -> 10.0.3
Where did you install Nextcloud from:
official tarball
Signing status:
No errors have been found.
List of activated apps:
Enabled:
The content of config/config.php:
{
"system": {
"instanceid": "ocq05beinini",
"passwordsalt": "***REMOVED SENSITIVE VALUE***",
"secret": "***REMOVED SENSITIVE VALUE***",
"trusted_domains": [
"aaa.bbb.net"
],
"datadirectory": "\/var\/www\/nextcloud-data",
"overwrite.cli.url": "http:\/\/aaa.bbb.net",
"dbtype": "mysql",
"version": "9.1.3.2",
"dbname": "nextcloud",
"dbhost": "localhost",
"dbport": "",
"dbtableprefix": "oc_",
"dbuser": "***REMOVED SENSITIVE VALUE***",
"dbpassword": "***REMOVED SENSITIVE VALUE***",
"logtimezone": "UTC",
"installed": true,
"loglevel": 0,
"memcache.distributed": "\\OC\\Memcache\\Redis",
"memcache.local": "\\OC\\Memcache\\Redis",
"memcache.locking": "\\OC\\Memcache\\Redis",
"redis": {
"host": "localhost",
"port": 6379
},
"maintenance": false,
"updater.release.channel": "stable"
}
}
Are you using external storage, if yes which one: local/smb/sftp/...
No
Are you using encryption: yes/no
No
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
No
Browser:
Chrome 56
Operating system:
Windows 7
+1 Nextcloud 11.0.1
Clearly locking related @icewind1991 see https://help.nextcloud.com/t/duplicate-files-delete-not-possible/8869/4
+1
had this Problem with Nextcloud 11.0.3 as well.
@icewind1991 Can you take a look? This has been reported again at https://help.nextcloud.com/t/files-and-folders-shown-twice-in-web-ui/12416
will the fix be backported to 10 and 11?
thanks
will the fix be backported to 10 and 11?
First of all we need to fix it. But 10 is unlikely, because we plan to do a last release for 10 this month and then stop it (because two new mayor version are released and we plan to only support the last two mayor versions).
+1
11.0.2 (stable)
Trying again to summon @icewind1991 馃挴
Maybe it is Possible to set a Timeout for unlocking? After 10 hours or so it will automatically unlock?
Same Error here on Nextcloud 11.0.3
PHP 7.0.19-1~dotdeb+8.1
Debian 8
+1
Nextcloud 11.0.3
PHP 5.6.30-0+deb8u1
Debian 8
+1
Nextcloud 12.0.0
Is this related to this Bug?
https://github.com/nextcloud/server/issues/1166
Nextcloud Log:
Uncaught Error: Access to undeclared static property: OC\Files\Filesystem::$normalizedPathCache in /var/www/nextcloud/lib/private/Files/Filesystem.php:806 Stack trace: #0 /var/www/nextcloud/lib/private/Files/View.php(2018): OC\Files\Filesystem::normalizePath('/Henrik/files/K...') #1 /var/www/nextcloud/lib/private/Files/View.php(1156): OC\Files\View->unlockFile('/Kunden/Uniserv...', 1) #2 [internal function]: OC\Files\View->OC\Files\{closure}() #3 /var/www/nextcloud/3rdparty/icewind/streams/src/CallbackWrapper.php(109): call_user_func(Object(Closure)) #4 [internal function]: Icewind\Streams\CallbackWrapper->stream_close() #5 {main} thrown at /var/www/nextcloud/lib/private/Files/Filesystem.php#806
+1
Nextcloud 11.0.3
+1
Nexcloud 12.0.0
Summoning @icewind1991 the fourth time 馃檹
+1
Nexcloud 12.0.0
Summoning @icewind1991 the fifth time
In the meantime, is any workaround possible other than forbidding users to move folders from a share to another?
+1
Nextcloud 12.0
PHP 7
Can reproduce, looking into it
Fix is here: https://github.com/nextcloud/server/pull/5424
Thanks @plrunner for the detailed reproduction steps
Will this fix also fix problems if the files have NOT been shared but just moved from one folder to another through the desktop client and regular explorer in windows..? I'm having this error:

Even rescanning the filesystem did not change anything.
@christianromeni yeah, I've seen that too once or twice, not sure if it is related. Can't reproduce it either, it just happens sometimes. Copying the file to that location and removing it again fixes the complaints.
Seems fix #5424 works only partly for this issue. Tested on latest stable 12.
Files can be deleted now, but I still see some duplicates, some duplicates are not seen anymore.
Files can be deleted now, but I still see some duplicates, some duplicates are not seen anymore.
Mmmmh ... could you open this in a separate ticket and describe how you got those duplicates? Because it could also have a different cause. For multiple instances the problem described in here was solved by the PR. Thanks
Seems the fix was not complete. Re-opening for @icewind1991 to fix.
New fix is in #5770
Still not enough ;)
Same problem on latest 12.0, Will the fix if any be for version 12 or shall we have to wait till version NC13?
I have succeeded fixing the issue by removing the share, delete the folder then recreated and re-share it.
But this is far from a permanent solution.
Fixed in 12.0.1 and 13.
None of these versions are out yet.
Since there are some bug fixes, If I drag an empty folder from my computer into nextcloud it does not show, nor produce an error message.
The workaround is to sftp into nextcloud and copy the folder/folders or mkdir the folder then scan with occ.
This has been there since early days but now it is becoming urgent.
None of these versions are out yet.
But 12.0.1 is planned for next week
Great thank you.
Could you please look into the empty folder issue ?
Could you please look into the empty folder issue ?
Could you please open a new ticket for this (and first search if there is already one)
done thank you
https://github.com/nextcloud/server/issues/5828
A other user of my cloud told me , that he had this bug a couple of days. I dont know if on this time i had updated to 12.0.1 (12.0.2) already. I had the Bug about 3 times , but that was before Version 12.
This bug existed before version 12.0.1 .
It should not be there if you have done the upgrade to 12.0.1
thanks for than info
This bug is also in 12.0.0
This bug is also in 12.0.0
Then upgrade to 12.0.3 - as written: it was fixed in 12.0.1
+1
I got this bug:
https://help.nextcloud.com/t/duplicate-files-delete-not-possible/8869/7
The upgrade to 12.0.3 didn't solve the problem @MorrisJobke. FYI i had the 12.0.2 version when i got the same problem @tedd77.
The semi-solution that consist of clearing file_lock didn't work too @jospoortvliet.
Thanks for your help if someone found the solution
Same here with 12.0.3
@icewind1991 Regression in 12.0.3? Or missing repair step?
I had this but also in 12.0.2 no idea early versions
@icewind1991
I can repoduce the issue on a clean installation of 12.0.4.
The problem still occurs while using shared folders from the groupfolders app.
There are no problems with regular shared folders!
Groupfolders has known issues with sharing, you can try and see if https://github.com/nextcloud/server/pull/7323 fixes that problem
Still seeing this issue in 12.0.4

@DP19 the PR mentioned by Icewind will be in 12.0.5 - let us know if that fixes it (12.0.5 should come out in a week or two)
In a just upgreaded 12.0.5 the propblem seems still to exist
I am on 12.0.5 and just observed the same issue. The symptoms are also very well described here: https://help.nextcloud.com/t/files-and-folders-shown-twice-in-web-ui/12416
Workaround that fixed it for me was:
- on OS level: move (mv) the directory away
- on OS level: put a new copy (cp) in place of the very same directory and files (same location of course)
-- I accidentally forgot to set proper permissions for "www-data"- tried to delete that folder from users web ui -> err'd out because of lacking filesystem permission for webserver user
-- initially I wanted to follow the workaround described here:
https://help.nextcloud.com/t/csync-error-windows-client/8285/9- out of curiosity I just browsed into the folder (users web ui) and now the folder was showing proper filenames and no duplicates anymore already
-- yet it was showing a warning about lacking permission to change data inside that folder
-- decided to save the extra mile of the delete and just keep the folder and files as the symptom was gone- corrected permissions with chown & chmod
- ran files:scan on that folder to get rid of that (now false positive) permission warning
I am not sure, but if a "move out" and "copy back" just did the trick, then maybe a simple "touch" on all affected files and folders would be sufficient to fix/workaround that duplicate display issue.
Maybe someone with insight into the code could confirm whether the changed timestamp of the folder(s) and files or the permission issue caused NC to "fall back on its feet" / reset its view about the local filesystem - or was it the failed delete? There must be some code path that I triggered which re-evaluated the state of the FS and corrected the DB entries :)
Correction of workaround (did not properly recall the steps I went through, so please ignore the quoted text above):
- on OS level: move (mv) the affected directory away
- try to delete the folder from UI
-- this err'd out but the folder and all files inside are wiped from DB
-- reload on UI will confirm the folder is gone- on OS level: move (mv) original folder back in place
-- make sure it has proper FS permissions- run files:scan on that folder
HTH
From my experience, upgrading to a newer version of Nextcloud does not solve the problem for those folder already affected. This would explain why there are still people reporting the bug as open.
So the question for those still having the problem: does the creation time of your affected folders go back to when you were using a bugged Nextcloud version?
@icewind1991 ^
occ maintenance:repair --include-expensive should repair the invalid entries that were caused by this issue
on nextcloud 13.0 i've always same error, i've also do that command occ maintenance:repair --include-expensive but nothing change.
I am seeing this identical behavior with NextCloud v13.0.4.
@scrow did you do what icewind suggested:
occ maintenance:repair --include-expensive
I did, and it did not make any difference. I ended up abandoning NextCloud mainly due to the flaky external storage support, so to that end, I consider the issue "resolved."
Most helpful comment
+1
Nexcloud 12.0.0