Everyone should read HolgerK's answer. It's too ridiculous to be believed: He wouldn't copy anything to a computer that isn't connected to an UPS.HolgerK wrote:Definitely yes, if this will happen more than twice.knnknn wrote:You would refuse to use a server that can crash because of a power failure?
You, see you are talking theories, while I am talking practice. I copy several terabytes over LAN every month AND COPY ERRORS HAPPEN.HolgerK wrote:A solid system has several mechanism to guarantee the data integrity:
- Memory with parity.
- CRC checks on physical layers.
- Checksums on logical layers.
- RAID 1/5/6 hard disk mirroring/parity
- Backups
How in the world can anyone be AGAINST VERIFYING?
How do _YOU_ know that a copy error never happened on your systems, since you are against verifying?
And, no, Backups do not guarantee data integrity, since Backups without Copy+Verify are the very problem I am talking about.
Faulty memory will not warn you when copy errors happen.
Faulty RAIDs will also not warn you.
And, no, CRC checks won't protect from read errors.
And how do you know the new harddrive is working OK, if you don't copy+verify? You will notice after weeks/months that x% of your files have been corrupted. ANd maybe you will never notice if you MOVED your files without verifying.
Well, if _YOU_ don't need it then don't verify. You are the only one who should care about YOUR data. I and many other will surely welcome a verify function for the extra safety that it gives.HolgerK wrote:Seriously, you are talking about a imho in most cases unnecessary feature for a single program
I didn't write anything about "one after the other". Copy errors happen not often, but from time to time. THAT is EXACTLY the problem: That they DON'T HAPPEN OFTEN. Thus if you don't verify you will not notice maybe for YEARS.HolgerK wrote:, while the rest of the programs (including the OS) running on such scrappy hardware, is creating one erroneous file after the another.
I have a whole pile of hard drives that a broken. Some break over night, some break over time. A copy+verify function is a way to notice when a hard drive starts to fail or when memory (RAM) starts to fail.
Who says anything about "without any consequence"?HolgerK wrote:Creating & copying & verifying checksums on demand, to check your storage or network connection is one way, but without any consequence after detecting a possible source
Unfortunately you can only replace the faulty hardware if you copied+verified the data onto a new harddrive. TC already has a rudimentary copy+verify (in the form of synchronize folders) but synchronizing doesn't always work and IS ALWAYS FAR MORE COMPLICATED than checking a simple checkbox.HolgerK wrote:and replacing this faulty hardware