public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: 7v5w7go9ub0o <7v5w7go9ub0o@gmail.com>
To: for list <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Re: Fast checksumming of whole partitions
Date: Sat, 05 Jun 2010 13:39:17 -0400	[thread overview]
Message-ID: <4C0A8BC5.9040305@gmail.com> (raw)
In-Reply-To: <20100605063956.GA5125@solfire>

On 06/05/10 02:39, meino.cramer@gmx.de wrote:
[]
>
> Is there any faster and reliable way to checksum whole paritions (not
> on "per file" base)???


FWIW, portage has a tool called "dcfldd" that works well for me. It is
dd with the addition of:

      *   Hashing on-the-fly - dcfldd can hash the input data as it is
being transferred, helping to ensure data integrity.
      * Status output - dcfldd can update the user of its progress in
terms of the amount of data transferred and how much longer operation
will take.
      * Flexible disk wipes - dcfldd can be used to wipe disks quickly and
with a known pattern if desired.
      * Image/wipe Verify - dcfldd can verify that a target drive is a
bit-for-bit match of the specified input file or pattern.
      * Multiple outputs - dcfldd can output to multiple files or disks at
the same time.
      * Split output - dcfldd can split output to multiple files with more
configurability than the split command.
      * Piped output and logs - dcfldd can send all its log data and
output to commands as well as files natively.


e.g. when I copy my HD, I get a copy status report and hash by using the
following commands:

#!/bin/bash
dcfldd if=/dev/sda bs=4096k sizeprobe=if status=on hashwindow=0 of=/dev/sdb
dcfldd if=/dev/sdb bs=4096k sizeprobe=if status=on hashwindow=0 of=/dev/null

When they've completed, I'll visually compare the two hashes (you can
automate this.) You can get fancier and do the Verify instead of the hashes.

HTH

(p.s.  Part of your answer is setting the best blocksize for dd or
dcfldd.

I'd presume it the smaller of your available memory, or the buffer size
on your HD?...... someone please correct me on this!?)






  parent reply	other threads:[~2010-06-05 17:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05  6:39 [gentoo-user] Fast checksumming of whole partitions meino.cramer
2010-06-05  7:19 ` [gentoo-user] " Nikos Chantziaras
2010-06-07 15:48   ` meino.cramer
2010-06-07 17:10     ` walt
2010-06-07 18:47       ` meino.cramer
2010-06-07 17:31     ` Andrea Conti
2010-06-07 18:54       ` meino.cramer
2010-06-11 22:41         ` Mick
2010-06-05  7:32 ` [gentoo-user] " Andrea Conti
2010-06-05 17:39 ` 7v5w7go9ub0o [this message]
2010-06-05 19:23   ` [gentoo-user] " meino.cramer
2010-06-05 20:11     ` Manuel Klemenz
2010-06-06 19:02       ` 7v5w7go9ub0o
2010-06-06 19:47         ` Joerg Schilling
2010-06-06 22:43           ` 7v5w7go9ub0o
2010-06-06 23:12             ` Joerg Schilling
2010-06-06 22:46         ` Neil Bothwick
2010-06-07  1:04           ` 7v5w7go9ub0o
2010-06-05 23:44     ` 7v5w7go9ub0o
2010-06-06 10:19       ` Andrea Conti
2010-06-06 16:55         ` Mick
2010-06-06 18:55         ` 7v5w7go9ub0o
2010-06-06 20:00           ` Mick
2010-06-06 20:45           ` Andrea Conti
2010-06-06 23:06             ` 7v5w7go9ub0o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C0A8BC5.9040305@gmail.com \
    --to=7v5w7go9ub0o@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox