[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 4066]  Rename to different case leads to inconsistent state
From:       ktm1 () tigris ! org
Date:       2011-11-25 17:04:42
Message-ID: 20111125170443.010A5540087 () sc157-tigr ! sjc ! collab ! net
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=4066



User ktm1 changed the following:

                What    |Old value                 |New value
================================================================================
                Priority|P3                        |P2
--------------------------------------------------------------------------------




------- Additional comments from ktm1@tigris.org Fri Nov 25 09:04:42 -0800 2011 -------
I have got some more information about the problem: it occured to be more 
serious, so I changed the priority to P2.

We quickly figured out that the problem was not only with my working copy, but 
with working copies of all colleagues, and, even more, with freshly checked out 
working copies. That is: I check a clean working copy from the repository and I 
immediately get a modified file and a missing directory.

That means that the repository itself became corrupted which is of course a huge 
bug.

After that I found out that my colleague in fact not only performed a commit 
where he renamed directory 'Test' to 'test', but he also cancelled the commit in 
progress (by pressing the Cancel button in TortoiseSVN while the files were 
being commited).

So the problem was caused by "broken atomicity" of the commit. I presume that 
this was caused by a combination of  cancelling the commit and renaming (in the 
commit) directory name by only changing its case.

Luckily I finally found the workaround: I checked out the working copy in Linux 
where name case makes difference. Both 'test' and 'Test' had been placed to the 
working copy. Then I simply deleted these directories using 'svn delete' 
command. After that all problems with repositories of Windows users disappeared 
(had to resolve tree conflict first, but that was easy).

Well, even though the solution was found I think that breaking commit atomicity 
is a huge bug. I hope there will be no consequences of this incident but now I 
cannot be sure.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=2887131

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@subversion.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]