« Return to Thread: Commit failed + checksum mismatch

Re: Re: Commit failed + checksum mismatch

by Chris Chapman :: Rate this Message:

Reply to Author | View in Thread

I'm fairly sure it's possible to replicate this issue by cancelling a commit
at an awkward point. I have had issues when performing a commit on a remote
server (so it runs relatively slowly). If I click the big red cancel button
it does not cancel the commit straight away, rather it seems to run on
(maybe to the end of the current file)? But I have had serious issues come
up with my working copy from doing this. It looks very much like the commit
makes it to the server and gets assigned a revision number and all that, but
that SmartSVN does not show that.
Trying to do the commit again will result in a checksum mismatch. Updates
also don't do what they're supposed to - I can delete the local file and
perform an update, and the file that was committed gets pulled back down
from the server. But any attempt to commit that file at a later point (say
if a further change to the file was made) results in the checksum mismatch.
The only way to resolve the issue is to nuke the whole folder (including
.svn admin area) and pull it back down from the repository. Using the
SmartSVN functionality for 'rebuilding admin area' on Update does not help
either.

It's very possible the two issues are unrelated, but I think if it's
possible for the admin area to get corrupted on something simple like
cancelling a commit, then it's possible that it is also being corrupted by
other changes that happen mid-commit.

Sorry for the vague repro steps, but I'm unable to go through the process
and come up with the exact version right now.

C

On Thu, Feb 12, 2009 at 6:44 AM, davydik <davydik@...> wrote:

>   I have same problem on 3 Vista x32 machines. All XP machines works ok.
>
>
> --- In smartsvn@... <smartsvn%40yahoogroups.com>, "ZedUbal"
> <skrymsli@...> wrote:
> >
> > We don't have any SVN integration in Visual Studio. Using VS 2008.
> > At home I'm running 32-bit Vista and I don't recall having this
> > problem.
> >
> > --- In smartsvn@... <smartsvn%40yahoogroups.com>, syntevo
> Support <smartsvn@> wrote:
> > >
> > > > We've also noticed that closing Visual Studio before committing
> > changes
> > > > seems to prevent the error... still testing that theory.
> > >
> > > That sounds interesting and we would really appreciate your input
> > here. Is
> > > there any SVN integration in Visual Studio which might interfere
> > with
> > > SmartSVN?
> > >
> > > Visual Studio is definitely a common application; do other VS users
> > experience
> > > similar problems in combination with SmartSVN?
> > >
> > > --
> > > Best regards,
> > > Marc Strapetz
> > > _____________
> > > syntevo GmbH
> > > www.syntevo.com
> > >
> > >
> > >
> > > "ZedUbal" <skrymsli@> wrote:
> > >
> > > > Hello!
> > > >
> > > > Recently we switched over to Subversion from CVS. I have been a
> > > > longtime fan of smartcvs so I got smartsvn. Everything seems to
> > be
> > > > working well except some random errors that occur during commits.
> > I
> > > > am on Windows Vista x64 using version 5.0.4. Noticed these same
> > > > problems in 5.0.3 and 4.0.x.
> > > >
> > > > I've read posts on similar problems from other users, but nothing
> > in
> > > > those threads seems to apply or fix the problem.
> > > >
> > > > Details:
> > > >
> > > > Randomly during commits I will get a message "Commit failed
> > (details
> > > > follow): Unknown error". The commit fails and the files that I
> > was
> > > > trying to commit are still displayed as "modified" in smartsvn.
> > The
> > > > more files I commit at once, the more likely this error happens.
> > > >
> > > > After this happens I try to update and I get a message like:
> > > >
> > > > Update to HEAD: working copy '<directory>' locked; try performing
> > > > 'cleanup'
> > > >
> > > > I go to that directory and I select Modify->Cleanup. This always
> > > > removes the lock icon. Now I can update and when I do most of the
> > > > files change to an "unmodified" state, so they were actually
> > committed
> > > > successfully. One file will still show modified. When I attempt
> > to
> > > > commit that file I get a checksum mismatch error.
> > > >
> > > > This has probably happened to me about 30 times in the span of two
> > > > months. It is very frustrating. To fix the checksum mismatch I
> > end
> > > > up marking the file as replaced. The only other way I have found
> > to
> > > > fix this problem is to check out the file in a new location, copy
> > over
> > > > the modified file and then commit again. It seems that the local
> > > > metadata for the file gets corrupted somehow.
> > > >
> > > > I have a co-worker who is working on the same repository using
> > > > smartsvn on Linux. He never saw any problems like this. As soon
> > as
> > > > he started working on the code in Vista (using smartsvn) he
> > started to
> > > > see exactly the same problems on his machine. It seems to be
> > > > something specific to windows or vista. We've also noticed that
> > > > closing Visual Studio before committing changes seems to prevent
> > the
> > > > error... still testing that theory.
> > > >
> > > > Any ideas? What information or log files can I provide to help you
> > > > debug this problem?
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
>  
>


[Non-text portions of this message have been removed]



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/smartsvn/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/smartsvn/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:smartsvn-digest@...
    mailto:smartsvn-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    smartsvn-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

 « Return to Thread: Commit failed + checksum mismatch