Unfortunately I missed some answers post to this point.
Just for final clarification:
So *IS* svn verify checking complete integrity (data, structure, hardware, and all you told me), or is it *NOT*, and if not, is there a tool to check for that (as most RDBMS has one), or is there not?
Mit freundlichem Gruss / With kind regards
Markus KARG, Staatl. gepr. Inf.
Entwicklung / R & D
QUIPSY QUALITY GmbH
Von: Paul Koning [mailto:firstname.lastname@example.org]
Gesendet: Mi 05.10.2005 17:12
An: Markus Karg
Cc: email@example.com; firstname.lastname@example.org
Betreff: Re: AW: AW: How to check integrity of database?
>>>>> "Markus" == Markus Karg <email@example.com> writes:
Markus> I don't know the internal structures of FSFS, but what
Markus> happens if FSFS returns buggy data? Is svn verify checking
Markus> that the data is correct or does it trust on FSFS to never
Markus> return buggy data (i. e. data that looks correct but actually
Markus> is screwed: e. g. the original source line would be "class x"
Markus> but FSFS returns
Markus> "class y"
Markus> because of internal mislinked pages.
Markus> Can this happen in FSFS and if it happens, does svn verify
Markus> detect it?
If that is the sort of thing you're worried about, the issue isn't
structural integrity, but data integrity. While it's possible for the
database to mess this up, the file system could also do it. And the
hardware is the most likely cause of problems -- CPU, bus, memory, I/O
channels, disk drives...
As Matt England pointed out, if this is what you're worried about, the
only answer is going to be to generate and save checksums (md5sum or
better) for every file. You can then regenerate them and check for
You may also want to examine your hardware for unprotected data
paths. Typical PCs contain quite a bunch of those; server-grade PCs
probably fewer but the number may be nonzero even so.
Received on Thu Oct 6 07:45:19 2005