Skip to content
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

Closed
alexeymuranov opened this issue Nov 27, 2018 · 4 comments
Closed

Comments

@alexeymuranov
Copy link

alexeymuranov commented Nov 27, 2018

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

  1. Synchronise a synch_r folder on a Nextcloud server with a synch_l folder on a personal machine.
  2. Create in synch_l a symlink test to another folder external.
  3. Create in synch_r an actual subfolder test.
  4. Try to create a file in external an observe that it will not be synchronised with the remote folder.
  5. Try to create a file in synch_r/test and observe it to appear in the local external.

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

  1. Client logfile: Output of nextcloud --logwindow or nextcloud --logfile log.txt
    (On Windows using cmd.exe, you might need to first cd into the Nextcloud directory)
    (See also https://docs.nextcloud.com/desktop/2.3/troubleshooting.html#log-files)

  2. Web server error log:

  3. Server logfile: nextcloud log (data/nextcloud.log):

@alexeymuranov
Copy link
Author

It seems that file disappearance is confirmed in another scenario: #876 (comment).

@FlexW
Copy link

FlexW commented Sep 27, 2021

Does the issue still apply?

@github-actions
Copy link

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!

@github-actions github-actions bot added the stale label Oct 28, 2021
@github-actions
Copy link

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
Projects
None yet
Development

No branches or pull requests

4 participants