FreeFileSync Forum

therube -- that would be an excellent depth-first iterative approach if the program does indeed follow a depth-first algorithm. I'm not positive it does, but someone else can weigh in on that. It would be O(n) where n is the number of folders in the tree. Probably the minimum bounds you can have on ...

+1.

Running into this while attempting to copy the contents of a Backups.backupdb Time Machine backup to a new SparseBundle. I have, for now, turned on the option to ignore errors. I did ask the program to copy file access permissions/ACLs, hoping that it would know that escalation is required. The ...

Right -- I certainly wouldn't be advocating for an algorithm that creates a performance hit across the board, but perhaps an "Advanced FS compatibility detection" setting would allow some performance hit to do some benchmarking and understand what additional considerations (i.e., <=O(N) performance ...

This thread was linked from a (duplicate) post I made a couple of days ago. I'd like to add my 2c that the importance of modified dates in folders has to do with indexing/sorting and search functions. If I'm looking for something with Spotlight, it pays attention to these modified folder dates. That ...

I see this has already been discussed here: viewtopic.php?t=6123

I'm transferring large folder trees right now and running into a problem whereby the files in the job are preserving date/time info, but the folders are not. Any zero-file folders are fine, but folders with files inside will ultimately fail. Considering the algorithm as I understand it currently, I ...

Yes, that's something I alluded to in my initial post. I understand that position, but there are quite a few aspects here that make this worth looking at (and talking about) rather than just dismissing it out of hand because it seems uncommon. I don't really argue that point, necessarily, but this ...

Yes it is, but sometimes you don't get to choose what happens with massive data moves and merges from multiple file structures. ;-) The point is to handle the error case gracefully, not to make a case for developing this error case intentionally.

As an aside, technically FFS could detect the capability of the underlying filesystem by intentionally writing a file and attempting to access it with reversed casing. That would infer the capability of the access method and thereby allow the conclusion that it were capable/not capable of allowing ...

Yes that is correct -- the detection would be that there are two references for the same location/contents. This is inferred by the CIFS access method paired with the case-insensitive collision. It could easily be a warning generated in the log that clues the user in to the possibility of an ...

Greetings. I've recently started using your software for a major data migration from a Drobo5N NAS so that I can upgrade the underlying filesystem of the array. In the process, I've discovered a strange situation which might be experienced by few others, but your software could help alleviate the ...