On 29-Jun-07, at 11:00 AM, david.x.grierson@jpmorgan.com wrote:
> The problem is that hardware faults and errors don't just occur on the
> server side where you have significant control over them - they can
> often
> occur on the client as well.
>
> I experienced a situation where a repository of another SCM tool was
> corrupted because the client network driver was erroneously inserting
> nulls into files while they were being transferred across the network.
>
> We were initially unaware of the issues because the SCM solution was
> (correctly) recording the contents of the files which were being
> presented
> to it as the new revision and developers were going on continuing
> their
> development.
>
> Eventually (a week or so later) they were unable to modify the objects
> which had become corrupted. Fortunately the SCM system had tools
> for going
> through the repository identifying the components which were
> corrupted and
> then recovering their contents appropriately.
Subversion can recover from this situation without data loss using
its ordinary tools. It's not a situation where server side recovery
is indicated.
(I wonder if your anecdote is about VSS, which by design is just data
loss waiting to happen.)
--Toby
>
> If you're in a job where you're able to turn around to management
> and say
> "sorry we've lost the last week's worth of development & it'll all
> just
> have to be done again because our SCM system doesn't let us fix
> things"
> then you're in a position of real power.
>
> Dg.
> --
> David Grierson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 29 16:49:17 2007