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

Re: recent client-side corruptions and Alpha

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2002-07-12 23:43:21 CEST

On 12 Jul 2002, Philip Martin wrote:

> Justin Erenkrantz <jerenkrantz@apache.org> writes:
>
> > On Fri, Jul 12, 2002 at 10:18:35PM +0100, Philip Martin wrote:
> > > I suppose the hash could have been corrupted, in which case the bug
> > > could be almost anywhere. Another alternative is that the names used
> > > to lock and to retrieve don't match, a trailing slash or something.
> > > That's why I would like to know the exact command line parameters.
> >
> > Yeah, I ran into the case where we sometimes had a trailing slash
> > and other times we didn't. I protected myself with calls to
> > the canonicalize function. -- justin
>
> As far as I can see this doesn't explain the server corruption, so I
> think this is a red herring. Anyway I've tried lots of combinations
> of file and directory targets with and without trailing slashes, and I
> can't reproduce the crash.

Last night I created a brand new repo and one of the first things I did
was to set some properties on the trunk directory and try to add files all
in the same commit. That is when I got my hang when trying to add files
and by the time I got things settled down it had corrupted a file.

I could try it again and see if I can reproduce it in a few hours when I
get home......

-- 
David Wayne Summers          "Linux: Because reboots are for upgrades!"
david_at_summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 12 23:43:52 2002

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.