Dynamic change in file boundaries are ignored because of the file last modified time
Closed this issue · 1 comments
Suppose client has some version of a file.
On server nothings has changes since the client download that version, except the boundaries, suppose file was expanded and new 100 bytes of data become tracked but first 100 bytes of file become untracked (file on disk itself left untouched though). Server tracks the same file, the length is also the same, however it reads file with kind of an offset.
Imagine clients connects to download a new version of the file. Rsynk sees that servers and clients file sizes and last modified times are identical and it doesn't send the new version of that file.
The bug is fixed.
All files are track the last cached value of boundaries. If such event occurs, the last modified time is incremented by one.