On Sat, May 3, 2008 at 8:37 PM, John Peacock
<john.peacock_at_havurah-software.org> wrote:
> Yakov Lerner wrote:
>
> > Which svn command can be used to validate internal consistency
> > of working copy again corruption in particular all files under .svn ?
> >
>
> You're thinking of git; that's down the hall, through the double doors,
> down the flight of stairs, and out into the parking lot in back.
>
> Tell us what symptoms you are actually seeing (i.e. your problem) rather
> than leaping ahead to some proposed "solution" that isn't valid here.
Svn is exceptionally reliable. I never heard of corrupted repo.
However, corrupted
working copy happened, and happened to other users ( search dev mailing list ).
I had my share of corrupted working copies; although the
fix is very easy -- just do 'svn co' afresh --
-- I want to be able to diagnose the case of corrupted working copy
in order to clearly distinguish it from other errors. Maybe some existing svn
command already does the validation ?
Sorry John, both your assumptions are wrong:
1) I am not thinking of git. This is your wrong assumption #1.
I am thinking the reliabiliity of svn, and about tool that let me diagnose
problem of working copy.
2) If you assume that "corrupted working copy" never happens,
this is your another wrong assumption.
In filesystem design, they say "corruption because of bad cables,
controller malfunction, disk malfunction" (BTW I had once FS corruption
caused by faulting RAM - Y.L).
For working copy, everything that causes FS corruption would cause
WC corruption, plus maybe disk full, too, maybe perms change on metafiles.
Yakov
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-14 08:12:46 CEST