| 1 |
On 06/05/2010 09:39 AM, meino.cramer@×××.de wrote: |
| 2 |
> |
| 3 |
> Hi, |
| 4 |
> |
| 5 |
> this night dd copies the contents of my first |
| 6 |
> 1TB disk to my second 1TB disk (same Model). |
| 7 |
> |
| 8 |
> (dd if=/devsda of=/dev/sdb bs=4096) |
| 9 |
> |
| 10 |
> I want to verify, that the copy is identical. |
| 11 |
> |
| 12 |
> I tried (or: I am still trying) to checksum |
| 13 |
> the first disk with |
| 14 |
> |
| 15 |
> whirlpooldeep /dev/sda |
| 16 |
> |
| 17 |
> whch seems to work but is DAMN slow (in relation |
| 18 |
> to checksumming 1TB in whole). |
| 19 |
> |
| 20 |
> Is there any faster and reliable way to checksum |
| 21 |
> whole paritions (not on "per file" base)??? |
| 22 |
> |
| 23 |
> Thank you very much in advance for any help! |
| 24 |
> |
| 25 |
> Best regards, |
| 26 |
> mcc |
| 27 |
|
| 28 |
Constructing a checksum means reading every byte off the partition. So |
| 29 |
it's slower as a copy to /dev/null, never faster (because the checksum |
| 30 |
calculation also needs time.) |
| 31 |
|
| 32 |
So in order to determine whether it's really slow, compare the time |
| 33 |
needed to dd the whole partition to /dev/null to the time needed for |
| 34 |
checksumming it. Then post the times here and an expert might then tell |
| 35 |
whether this can be improved at all or not. |
Archives