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

False-positives for changed files, when sideloading to speed up Send Only folders #8167

Closed
OCRenkist opened this issue Feb 7, 2022 · 1 comment
Labels
bug A problem with current functionality, as opposed to missing functionality (enhancement) frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion needs-triage New issues needed to be validated

Comments

@OCRenkist
Copy link

OCRenkist commented Feb 7, 2022

False-Positives for Changed Files, when Sideloading to Speed up Send Only Folders

Operating Systems Tested

Mainly GNU/Linux (mostly version 19.3 of the Linux Mint distribution), and Android/Linux versions 9 and 10.

Syncthing Versions Tested

Most every version of Syncthing since the introduction of the Send Only folder type.

What Happens
  1. Create a Send Only folder.
  2. Share the folder with another device.
  3. Synchronization begins.
  4. Observe the network transfer rate is slower than that of USB.
  5. Copy the files from the Send Only device to the target device via USB.
  6. Syncthing on the both devices observes there are new files on the target device.
  7. Syncthing on the target device checksums the new files.
  8. Despite the new files being identical to the files on the Send Only device,
    Syncthing on the target device offers to Revert Local Changes if
    the target folder is Receive Only and moves the new files to a versioning
    directory if Send & Receive, appending their names with a date-deleted timestamp.
Workaround

Setting the folder on both devices to Send & Receive appears to provide the expected behavior, but is a perilous solution when the files on the source device are supposed to be kept immutable.

Expected to Happen

Presumably, Syncthing would see during the checksum process upon detecting new files, that the new local files are identical to the remote files, and acknowledge this with an appropriate jump in percentage completed in the synchronization process. Ideally, Syncthing on the target device would touch the files with the correct mtime values from the Send Only device as well.

@OCRenkist OCRenkist added bug A problem with current functionality, as opposed to missing functionality (enhancement) needs-triage New issues needed to be validated labels Feb 7, 2022
@OCRenkist OCRenkist changed the title False-Positives for Changed Files, when Sideloading to Speed up Send Only Folders False-positives for changed files, when sideloading to speed up Send Only folders Feb 7, 2022
@AudriusButkevicius
Copy link
Member

Thats expected. Override changes would resolve this without data transfers, or setting the folder to send receive as you suggested.

Please use the forum if you want to further discuss this.

@calmh calmh added the frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion label Mar 10, 2023
@syncthing syncthing locked and limited conversation to collaborators Mar 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug A problem with current functionality, as opposed to missing functionality (enhancement) frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion needs-triage New issues needed to be validated
Projects
None yet
Development

No branches or pull requests

3 participants