1 |
On 06/05/10 02:39, meino.cramer@×××.de wrote: |
2 |
[] |
3 |
> |
4 |
> Is there any faster and reliable way to checksum whole paritions (not |
5 |
> on "per file" base)??? |
6 |
|
7 |
|
8 |
FWIW, portage has a tool called "dcfldd" that works well for me. It is |
9 |
dd with the addition of: |
10 |
|
11 |
* Hashing on-the-fly - dcfldd can hash the input data as it is |
12 |
being transferred, helping to ensure data integrity. |
13 |
* Status output - dcfldd can update the user of its progress in |
14 |
terms of the amount of data transferred and how much longer operation |
15 |
will take. |
16 |
* Flexible disk wipes - dcfldd can be used to wipe disks quickly and |
17 |
with a known pattern if desired. |
18 |
* Image/wipe Verify - dcfldd can verify that a target drive is a |
19 |
bit-for-bit match of the specified input file or pattern. |
20 |
* Multiple outputs - dcfldd can output to multiple files or disks at |
21 |
the same time. |
22 |
* Split output - dcfldd can split output to multiple files with more |
23 |
configurability than the split command. |
24 |
* Piped output and logs - dcfldd can send all its log data and |
25 |
output to commands as well as files natively. |
26 |
|
27 |
|
28 |
e.g. when I copy my HD, I get a copy status report and hash by using the |
29 |
following commands: |
30 |
|
31 |
#!/bin/bash |
32 |
dcfldd if=/dev/sda bs=4096k sizeprobe=if status=on hashwindow=0 of=/dev/sdb |
33 |
dcfldd if=/dev/sdb bs=4096k sizeprobe=if status=on hashwindow=0 of=/dev/null |
34 |
|
35 |
When they've completed, I'll visually compare the two hashes (you can |
36 |
automate this.) You can get fancier and do the Verify instead of the hashes. |
37 |
|
38 |
HTH |
39 |
|
40 |
(p.s. Part of your answer is setting the best blocksize for dd or |
41 |
dcfldd. |
42 |
|
43 |
I'd presume it the smaller of your available memory, or the buffer size |
44 |
on your HD?...... someone please correct me on this!?) |