Why using conv=notrunc when cloning a disk with dd?

Viewed 44307

If you look up how to clone an entire disk to another one on the web, you will find something like that:

dd if=/dev/sda of=/dev/sdb conv=notrunc,noerror

While I understand the noerror, I am getting a hard time understanding why people think that notrunc is required for "data integrity" (as ArchLinux's Wiki states, for instance).

Indeed, I do agree on that if you are copying a partition to another partition on another disk, and you do not want to overwrite the entire disk, just one partition. In thise case notrunc, according to dd's manual page, is what you want.

But if you're cloning an entire disk, what does notrunc change for you? Just time optimization?

1 Answers
Related