All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Heinz-Josef Claes <hjclaes@web.de>
Cc: Russell Coker <russell@coker.com.au>, reiserfs-list@namesys.com
Subject: Re: How to build a big file server
Date: Thu, 05 Jun 2003 18:47:32 +0200	[thread overview]
Message-ID: <3EDF7424.7010003@gmx.net> (raw)
In-Reply-To: <1054809903.1995.83.camel@wusel.schnulli.de>

Heinz-Josef Claes wrote:
From the debian web page:
>
> http://packages.debian.org/testing/utils/storebackup.html
>
> File comparisons are done with MD5 checksums, so no changes go
> unnoticed.

If you believe the last sentence, I have a bridge to sell.

To be more exact: MD5 is a 128=2^7 bit hash. Assuming a file length of 4kB
= 2^8*4096=2^20 bits, approximately 2^(2^(20-7))= 2^8192= 10^2457
different files have the same hash.

That's right: for a given MD5 hash, there are more different files with
4kB size sharing the same hash than the count of atoms in the whole
universe. If the files are larger, it gets worse.

md5sum(1) is not diff(1). Most of the time, it will suffice as el cheapo
replacement, but for backups it's definitely horrible. You don't store
your backup tapes in the microwave, do you?


Carl-Daniel

-- 
http://www.hailfinger.org/


  reply	other threads:[~2003-06-05 16:47 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  8:14 How to build a big file server Heinz-Josef Claes
2003-06-05  8:25 ` Carl-Daniel Hailfinger
2003-06-05  8:55   ` Andreas Dilger
2003-06-05  9:51     ` Hendrik Visage
2003-06-05  8:33 ` Ragnar Kjørstad
2003-06-05  8:42   ` Heinz-Josef Claes
2003-06-05  8:45     ` Marc-Christian Petersen
2003-06-05  9:30       ` Heinz-Josef Claes
2003-06-05 11:27       ` Bill Rees
2003-06-10 13:28       ` myciel
2003-06-10 13:36         ` Heinz-Josef Claes
2003-06-10 14:13           ` myciel
2003-06-12 20:34             ` Lars O. Grobe
2003-06-05  8:46   ` Oleg Drokin
2003-06-05  8:50     ` Heinz-Josef Claes
2003-06-05  9:04       ` Oleg Drokin
2003-06-05  9:17         ` Heinz-Josef Claes
2003-06-05 10:29           ` Russell Coker
2003-06-05 10:45             ` Heinz-Josef Claes
2003-06-05 16:47               ` Carl-Daniel Hailfinger [this message]
2003-06-05 17:01                 ` Soeren Sonnenburg
2003-06-05 17:06                 ` Ragnar Kjørstad
2003-06-06  9:41                   ` Heinz-Josef Claes
2003-06-05 13:38           ` Hans Reiser
2003-06-05 12:06         ` Heinz-Josef Claes
2003-06-05  9:45 ` Christophe Saout
2003-06-05 10:07   ` Soeren Sonnenburg
2003-06-05  9:59 ` Russell Coker
2003-06-05 10:13   ` Heinz-Josef Claes
2003-06-05 10:25     ` Russell Coker
2003-06-05 10:38       ` Heinz-Josef Claes
2003-06-05 11:11         ` Russell Coker
2003-06-05 13:48       ` Chris Mason
2003-06-14 11:11         ` data-logging for 2.4.21+ (was Re: How to build a big file server) Manuel Krause
2003-06-05 10:05 ` How to build a big file server Hans Reiser
2003-06-05 10:24   ` Heinz-Josef Claes
2003-06-05 13:43 ` Sam Vilain
2003-06-05 13:55   ` Heinz-Josef Claes
2003-06-06 11:15   ` Vitezslav T. Se'm
2003-06-06 15:15     ` Russell Coker
2003-06-06 11:16   ` Vitezslav T. Se'm
     [not found] <no.id>
2003-06-05 23:49 ` The Amazing Dragon

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=3EDF7424.7010003@gmx.net \
    --to=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=hjclaes@web.de \
    --cc=reiserfs-list@namesys.com \
    --cc=russell@coker.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.