Client refuses to downsync with case sensitivity conflict, after the already downloaded inode is deleted, and only the not-synced one exists in server.

nextcloud / desktop

💻 Desktop sync client for Nextcloud

https://nextcloud.com/install/#install-clients

GNU General Public License v2.0

2.98k stars 784 forks source link

Client refuses to downsync with case sensitivity conflict, after the already downloaded inode is deleted, and only the not-synced one exists in server. #3162

Open jtagcat opened 3 years ago

jtagcat commented 3 years ago

How to use GitHub

Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.

Steps to reproduce

Client already has Foobar folder synced. Server-side, foobar folder is added.
Server has 2 folders. Foobar and foobar.
Client rightfully refuses to sync, detecting a conflict.
foobar directory is deleted via the WebUI, leaving only the Foobar folder.
Client is restarted.
Client refuses to sync, after multiple restarts, force syncs, clears with the same error. Removing and re-adding the folder seems to be the only resolution now.

Client configuration

Using VFS.

Client version: 3.2.0

Operating system: w10

OS language: EN

FlexW commented 3 years ago

Did you check if this error also happens without using virtual files?

allexzander commented 3 years ago

I guess I have experienced something similar with both .png and .PNG created on Linux or via the Web UI, but, erroring with the VFS enabled. Yet, the sync was successful, it's just those errors always pop up. We may want to come with a fix for 3.2.1-3.2.2.

jtagcat commented 3 years ago

I was about to say can't replicate this now, but I can.

What I did:

setup sync client, vfs
First sync is completed.
Server state: created foobar and Foobar
Foobar is synced to device, foobar is skipped
delete foobar from cloud
client syncs fine
create foobar in cloud, delete Foobar in cloud (server state, newer: only foobar exists)
Client state: Foobar is synced, conflict with foobar
~~jctest_case_sensitivity_conflict.zip~~

Third replication:

setup sync client, normal, non-vfs
Cloud change: create foobar, Foobar dirs (added ~5 different textfiles to both)
Client: Foobar is downloaded/synced. foobar is skipped due to case sensitivity conflict error.
Cloud change: delete Foobar
Client: Still erroring, even after force sync now, and restart of the app. (expected: Foobar is deleted locally, foobar is synced) jctest_non_vfs.zip

Edit: Tested this with remotely renaming bazfile to Bazfile, renaming doesn't cause conflicts, so it's a more minor conflict.

jtagcat commented 3 years ago

Deleting the conflicting inode also on the client is a working workaround.

github-actions[bot] commented 3 years ago

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!

jtagcat commented 3 years ago

unstale

github-actions[bot] commented 3 years ago

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!

jtagcat commented 3 years ago

unstale

github-actions[bot] commented 3 years ago

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!

jtagcat commented 3 years ago

unstale :(