samba-bugs at samba.org
2015-Jan-03 21:23 UTC
[Bug 2294] Detect renamed files and handle by renaming instead of delete/re-send
https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #22 from elatllat at gmail.com --- Wow 10 years. Maybe one reason this has not been implemented is there are other options. For example I have been using a shell script as a wrapper to reduce the iteration of this bug, here is how it works: 1) Create 2 lists of files; destination and source with the files sizes and path 2) For each file that is in the destination but not the source 3) Create a subset of the source list containing file of the same size 4) If the subset > 0 hash the destination file and each file in the source subset until a match is found 5) Ensure the dir exists on the destination and move/rename the file. 6) On some systems hash can be as expensive as re-transferring the file so I added an option to move the file if there was one match (only sometimes hashing), and another to skip if more(never hashing). Though as I am re-evaluating my backup strategy I am looking into git-annex and other solutions. https://en.wikipedia.org/wiki/List_of_backup_software#Free_software -- You are receiving this mail because: You are the QA Contact for the bug.
Joe
2015-Jan-07 23:12 UTC
[Bug 2294] Detect renamed files and handle by renaming instead of delete/re-send
Isn't this pretty much what specifying --fuzzy --fuzzy (twice) is supposed to do? Joe On 01/03/2015 04:23 PM, samba-bugs at samba.org wrote:> https://bugzilla.samba.org/show_bug.cgi?id=2294 > > --- Comment #22 from elatllat at gmail.com --- > Wow 10 years. > Maybe one reason this has not been implemented is there are other options. > For example I have been using a shell script as a wrapper to reduce the > iteration of this bug, here is how it works: > 1) Create 2 lists of files; destination and source with the files sizes and > path > 2) For each file that is in the destination but not the source > 3) Create a subset of the source list containing file of the same size > 4) If the subset > 0 hash the destination file and each file in the source > subset until a match is found > 5) Ensure the dir exists on the destination and move/rename the file. > 6) On some systems hash can be as expensive as re-transferring the file so I > added an option to move the file if there was one match (only sometimes > hashing), and another to skip if more(never hashing). > > Though as I am re-evaluating my backup strategy I am looking into git-annex and > other solutions. > https://en.wikipedia.org/wiki/List_of_backup_software#Free_software >
Maybe Matching Threads
- [Bug 2294] Detect renamed files and handle by renaming instead of delete/re-send
- [Bug 2294] Detect renamed files and handle by renaming instead of delete/re-send
- DO NOT REPLY [Bug 2294] Detect renamed files and handle by renaming instead of delete/re-send
- [Bug 2294] Detect renamed files and handle by renaming instead of delete/re-send
- [Bug 2294] Detect renamed files and handle by renaming instead of delete/re-send