Hi,
I use BC3 often to copy large amounts of data and also to compare versions of folders. These can often be many TBs of data and hundreds of thousands of files, many of which are tiny, obscure, hidden, system, etc. Often there are files with long file names, which are buried deep in nested folders, and the total location/name are too long for windows to manage. In those cases I can skip over the offending files in windows, and then come back and do a second pass with BC3 to make up the difference, or sometimes I just use BC3 to do the entire copy from the beginning.
I often run into a situation where BC3 says two folders are the same, but if I right click on both folders in windows and get properties, the file count and file size are listed as different in windows. Sometimes it might be only a few files, or not much file size, sometimes it can be a lot.
I'm working on a folder now which is a good example. It's from a version control software which creates its own internal structure which is completely "insane" in terms of very lengthy, non-sensical, and deeply nested files and folders. It has many tens of thousands of tiny files that are only a few K. I did the copy using BC3, which says both folders are the same, but if I right click on the source folder, windows says it has around 8000 more files, and around 11GB more data than the destination folder.
I need to resolve if I should trust BC3, or windows, and it would help also to understand more about where the discrepancy comes from. I've seen this on many different machines (all windows), many different OS, many different file types, so its not a one time thing, or specific to my current computer, or this specific copy, etc.
Any help much appreciated.
I use BC3 often to copy large amounts of data and also to compare versions of folders. These can often be many TBs of data and hundreds of thousands of files, many of which are tiny, obscure, hidden, system, etc. Often there are files with long file names, which are buried deep in nested folders, and the total location/name are too long for windows to manage. In those cases I can skip over the offending files in windows, and then come back and do a second pass with BC3 to make up the difference, or sometimes I just use BC3 to do the entire copy from the beginning.
I often run into a situation where BC3 says two folders are the same, but if I right click on both folders in windows and get properties, the file count and file size are listed as different in windows. Sometimes it might be only a few files, or not much file size, sometimes it can be a lot.
I'm working on a folder now which is a good example. It's from a version control software which creates its own internal structure which is completely "insane" in terms of very lengthy, non-sensical, and deeply nested files and folders. It has many tens of thousands of tiny files that are only a few K. I did the copy using BC3, which says both folders are the same, but if I right click on the source folder, windows says it has around 8000 more files, and around 11GB more data than the destination folder.
I need to resolve if I should trust BC3, or windows, and it would help also to understand more about where the discrepancy comes from. I've seen this on many different machines (all windows), many different OS, many different file types, so its not a one time thing, or specific to my current computer, or this specific copy, etc.
Any help much appreciated.
Comment