Brian W. Fitzpatrick wrote:
On Fri, 2004-06-11 at 13:15, Stefano Mazzocchi wrote:
Pier Fumagalli wrote:
On 11 Jun 2004, at 22:02, Jim Moore wrote:
Actually, the "all or nothing" part of the transaction isn't a big deal because, as you said, it's very rare that a commit in CVS would fail.
Problem being (though) is that I've seen Subversion (1.0.2 under Linux) fail right because of that... Somehow an "atomic" transaction was left open on the server, don't ask me why...
Basically, after that commit failed, the entire repository was so slow that most TCP/IP connections were failing after 3 minutes for timeouts...
Only solution was to run a "svn recover" followed by a "svn rmtxt" and again followed by another "svn recover"...
I am experiencing random svn corruptions with svnserve over ssh with svn 1.0
Please be careful to distinguish "corruption" from "my repository needs to have 'svnadmin recover' run on it."
Could you be running into a repository permissions error?
http://subversion.tigris.org/project_faq.html#permissions
(how do I find out the real version btw? why isn't svn -v|--version give me the version?) over linux 2.6.4
any clue?
'svn --version' works for me:
$ svn --version svn, version 1.0.2 (r9423) compiled Apr 28 2004, 17:16:48 ...
hit me with a baseball bat!
-- Stefano, crawling back in his corner :-(
smime.p7s
Description: S/MIME Cryptographic Signature
