I had a client recently who thought I'd be copying data and try read of the same drive at the same time - and according to him it's something you can't do because you'd damage the data/hard-drive.
I still couldn’t find any information as to why you can’t read and write on the same drive ‘at the same time’; I thought this is what hard drives are meant to do: writing and reading requests are split into sub-processes, which are then executed, not 'simultaneously', but one by one. You usually try to avoid reading and writing on the same drive ‘simultaneously’ - because this back and forth, and sharing only one connection, slows down both processes in the end. But that’s for speed considerations, not data or hardware safety - I thought.
It is ‘safer’ to first finish a copy as quickly as possible, before doing anything else - just because the chances of a power failure, anyone spilling a coffee or bumping your hard drive etc are obviously slimmer in a shorter period of time than in a longer one. But otherwise:
Can reading of a drive while copying onto it 'damage' the data you are writing, or the hard-drive itself?
If yes: How?