SVN Commit Error (couldn't perform atomic operation)

Question

Everything was working fine, when all of a sudden, I am getting a

svn: Commit failed (details follow):
svn: Couldn't perform atomic initialization

What could the problem be ?

I am using "projectlocker" (http://projectlocker.com/)

OS: Ubuntu10.04

score 23 · Answer 1 · answered May 25 '14 at 07:51

23

In my case, it was because the partition that svn had been installed in, was full.

answered May 25 '14 at 07:51

1

This was my issue as well. Once I freed-up disk space, the commit worked fine. – Travitron Aug 02 '14 at 19:38
1

Thank you so much, that was the issue! – Nickolas de Luca Alberton Aug 22 '19 at 11:37
1

I faced the same issue, In my case, The root folder '/' was full in the svn server. – AlexYu Mar 03 '22 at 06:32
this works, our server was full – dotrinh PM Jan 19 '23 at 04:47

C. Tewalt · Answer 2 · 2018-12-12T22:43:15.940

14

Make sure there is space on your SVN Server's hard drive partition!

I noticed the same behavior. Wait a couple minutes then it worked. But that didn't always fix the problem. After looking at our SVN server we found that one of the partitions (the one that the server was on) was chalk full.

I had our IT guy clean up some of the space and everything worked nice and slick after that.

edited Dec 12 '18 at 22:43

answered May 01 '14 at 22:40

C. Tewalt

2,271
2
30
49

My "partition full" answer was first! :D – C. Tewalt Dec 12 '18 at 22:41

score 7 · Accepted Answer · answered Jan 26 '12 at 00:38

7

Weird, it started working fine, after about 15 mins.

I did not do anything.

answered Jan 26 '12 at 00:38

Prakash Raman

13,319
27
82
132

6

Started working after 15 minutes? Your "asked" and "answered" times are only a minute apart. – Ben Barden Dec 30 '13 at 15:08
@BenBarden, he said 15 minutes to make his answer more statistically likely of being right, lol. – C. Tewalt May 01 '14 at 22:42
9

@BenBarden it took him 14 minutes to log into SO and write the question – johnnycardy Jun 05 '14 at 11:26
@BenBarden, Matrixugly, johnyycardy :) Hehhehe Yes, it was a white ago - don't remember if it took me 14 minutes to get onto SO. Or I just lied :) – Prakash Raman Feb 05 '16 at 03:50
5

This is not an answer. One of the common reasons that this exception is being thrown is when the svn server or the local machine have no disk-space left. – Adi Darachi Mar 14 '16 at 17:36

score 4 · Answer 4 · answered Apr 30 '13 at 05:39

4

I have faced the similar issue.

Cause - file system became read only. fix - reboot the server

answered Apr 30 '13 at 05:39

user1307227

41
1

1

I had the same issue. In my case, the reason it became read-only was that it ran out of space on the hard drive, so the fix was a bit more involved, but still essentially the same cause. – Ben Barden Dec 30 '13 at 15:06

score 0 · Answer 5 · answered Jun 11 '13 at 16:52

In my case this was caused by the fact that apache was loading libphp5 module before mod_dav_svn and mod_authz_svn. The problem is that Apache is loading the implementation of libsqlite included in libphp5. So basically put LoadModule dav_svn_module and LoadModule authz_svn_module before LoadModule php5_module in your httpd.conf. This worked for me.

score 0 · Answer 6 · answered Feb 04 '16 at 01:30

0

Same issue.

Had 'PROPPATCH' and 'atomic initialization' issues.

Filesystem was okay..

FIX: restart the apache daemon.

answered Feb 04 '16 at 01:30

Ross

1,013
14
32

score 0 · Answer 7 · answered Aug 16 '18 at 05:59

I came across the same issue but mine was because of insufficient access privilege to /tmp folder which will be used by svn when creating a commit.

When I exam apache error log /var/log/apache2/error.log I saw [Thu Aug 16 13:46:39.498037 2018] [:error] [pid 78] [client 172.16.50.6:60010] Couldn't perform atomic initialization [500, #200029] [Thu Aug 16 13:46:39.498043 2018] [:error] [pid 78] [client 172.16.50.6:60010] Can't find a temporary directory: Internal error [500, #20014] So if anyone see these logs in your apache server's error log it might be the same reason as mine. After changing my /tmp access right to 777 the problem disappears.

score 0 · Answer 8 · answered Jul 23 '20 at 10:40

0

In my case I missed the space between 'create' and 'repo path'. I had the error message writing:

svnadmin create/repo_path

instead of

svnadmin create /repo_path

answered Jul 23 '20 at 10:40

Fil

1,032
13
29

SVN Commit Error (couldn't perform atomic operation)

8 Answers8