-
Notifications
You must be signed in to change notification settings - Fork 790
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Treating symlinks to folders seems badly broken in version 2.5.0 #899
Labels
Comments
10 tasks
It seems that file disappearance is confirmed in another scenario: #876 (comment). |
Does the issue still apply? |
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
File-eating bug
Expected behaviour
Either no modifications, or complete update to the latest versions both ways (synchronisation).
Actual behaviour
When the local synchronised folder contains a symlink to a folder while the remote synchronised folder contains an actual folder with the same name in the same location, strange things happen. A whole folderful of files can disappear without trace, or the synchronisation can happen only localwards.
I could reproduce disappearance of files in my existing folder, but not in a freshly created setup.
There were other strange and hard to reproduce behaviours: like not being able to synchronise an actual remote folder with a local folder symlink normally, while creating a new file in the remote folder would trigger synchronisation. I do not know how to describe or reproduce it, i can only summarise that it looks badly broken. (I do not know what the "correct" behaviour should be when there is a folder on one side and a symlink on another, but I am sure that not this one.)
Steps to reproduce
synch_r
folder on a Nextcloud server with asynch_l
folder on a personal machine.synch_l
a symlinktest
to another folderexternal
.synch_r
an actual subfoldertest
.external
an observe that it will not be synchronised with the remote folder.synch_r/test
and observe it to appear in the localexternal
.I also observed a behaviour that i didn't mange to reproduce from scratch yet, but constantly observed in my existing setup: the contents of a folder that was symlinked from inside a synchronised local folder was wiped out without trace on each synchronisation. Apparently it was related to the existence of an actual subfolder with the same name and in the same location in the remote synchronised folder.
Client configuration
Client version: 2.5.0-20181111.015125~bionic1
Operating system: Ubuntu 18.04
OS language:
Qt version used by client package (Linux only, see also Settings dialog):
Client package (From Nextcloud or distro) (Linux only):
Installation path of client:
Server configuration
Operating system:
Web server:
Database:
PHP version:
Nextcloud version:
Storage backend (external storage):
Logs
Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.
Template for output < 10 lines
Client logfile: Output of
nextcloud --logwindow
ornextcloud --logfile log.txt
(On Windows using
cmd.exe
, you might need to firstcd
into the Nextcloud directory)(See also https://docs.nextcloud.com/desktop/2.3/troubleshooting.html#log-files)
Web server error log:
Server logfile: nextcloud log (data/nextcloud.log):
The text was updated successfully, but these errors were encountered: