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

Weakness in spotting server-side file removal #998

hjohanns opened this Issue Jan 6, 2019 · 0 comments


None yet
1 participant
Copy link

hjohanns commented Jan 6, 2019

In my setup, clients write data into a local synced directory. In order to manage aging and space limitation, this data is tagged, and then the files_retention app is used to eliminate it after some time (some weeks).
The files_retention app works at the server level, and it is expected that the files are then removed from the client, but the mechanism breaks easily with large quantity of data.

Expected behaviour

When the files_retention app acts to delete data from the server, the expectation is that at next sync the same data is removed from the client local storage.

Actual behaviour

It has to be said that the mechanism works for small quantities of data. The data is effectively removed at next sync.
The problem is with larger quantities of data, that this mechanism interacts with the fact that synchronisation is automatically turned off by the client when the amount to sync exceeds a certain threshold (500MB in our case).
When synchronisation is turned back on, the mechanism sees files present on the client and absent on the server, and considers the client files as new files, so it copies them back on the server.

Steps to reproduce

  1. Setup a NC server with a NC client on Windows
  2. Create a large synced directory (larger than the setting shown in the screenshot).
  3. Sync turns off automatically for that directory
  4. Delete some content from that directory on the NC server with the browser interface
  5. Turn sync back on for the directory, files are copied again on the server.

Client configuration

Client version: Windows 2.3.3 (build 1)

Operating system: Windows 10

OS language: French

Installation path of client: C:/Program Files (x86)/Nextcloud

Server configuration

Operating system: Linux Ubuntu 18.04

Web server: Apache 2.4.29

Database: Mysql 8.0.13

PHP version: 7.2

Nextcloud version: 13.0.6

Storage backend (external storage): Local server disks


Need to collect the logs with the client (TODO)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment