public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] md5sum for directories?
Date: Sun, 24 Feb 2008 11:06:10 +0000	[thread overview]
Message-ID: <7B4F9B31-ABDE-47C7-B841-2D3902E7B3DD@stellar.eclipse.co.uk> (raw)

Hi there,

I'm in the habit of backing up customer data by booting from knoppix,  
connecting a portable hard-drive and copying with `cp -rvf`.

When this has finished I connect the portable hard-drive to my  
desktop machine, copy the directory of data from it to my homedir,  
and make a zip file of the directory.

I've done this loads in the past, and never been aware of any file  
corruption, but I guess I'm just paranoid today. Perhaps I shouldn't  
use the -v flags during my copy - it's reassuring to see the files  
being copied, but what if I overlooked a bunch of errors in the  
middle of all those thousands of "copied successfully" confirmations?  
What if something has gone wrong during one of the two copies?

So my question is:

Is there any way to check the integrity of copied directories, to be  
sure that none of the files or sub-directories in them have become  
damaged during transfer? I'm thinking of something like md5sum for  
directories.


It occurred to me that one could run `find . -type f -exec md5sum \{}  
\; > file.txt` on both machines and diff the outputs, but some of  
these directories contain many thousands of files, and I'd imagine  
that mdsumming of all these could take some time.

Does anyone have any suggestions, please?

Stroller.
  
   
-- 
gentoo-user@lists.gentoo.org mailing list



             reply	other threads:[~2008-02-24 11:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24 11:06 Stroller [this message]
2008-02-24 11:46 ` [gentoo-user] md5sum for directories? Etaoin Shrdlu
2008-02-27  0:38   ` Stroller
2008-02-27  9:40     ` Etaoin Shrdlu
2008-02-24 14:29 ` Neil Bothwick
2008-02-24 16:39   ` cabbage
2008-02-24 16:46     ` Dirk Heinrichs
2008-02-24 16:49     ` Andrew Gaydenko
2008-02-24 19:46 ` Christopher Copeland
2008-02-27  0:51   ` Stroller
2008-02-27  2:36     ` Christopher Copeland
2008-02-24 21:15 ` [gentoo-user] " »Q«
2008-02-26 19:59   ` Mick

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=7B4F9B31-ABDE-47C7-B841-2D3902E7B3DD@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --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