[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Checksums (Re: [PATCH]: svndiff version 1)

From: Zack Weinberg <zack_at_codesourcery.com>
Date: 2002-02-26 01:30:13 CET

This isn't strictly related to your changes, but since you're digging
around in this stuff anyway: I noticed not so long ago that the MD5
checksums stored in each diff representation were always all-bytes-zero.
I'm sure this is a straightforward bug to find and fix.

On a larger scale, I'd like to put forward the proposal that
*everything* we store in the database should have a checksum attached
to it. MD5 is probably overkill for everything but the strings table;
however, I want Subversion to detect and report immediately when a
disk block has gone south, causing a chunk of data in the middle of a
storage pool to be overwritten with NUL bytes.

This is not a hypothetical problem; it has happened repeatedly to
GCC's CVS repository. Because RCS doesn't validate ,v files, it can
go unnoticed for years, and then good luck finding a backup to restore
that block from.

Perhaps this is already taken care of by BDB, but then why do we have
checksums in svndiff representation entries?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:09 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.