On 2011-11-16, at 10:21 , Philip Martin wrote: > Aleksandr Sidorenko <asidore...@cashontime.com> writes: > >> Rebuilt, now I get this message on post-commit: >> >> Warning: post commit FS processing had error: >> Couldn't perform atomic initialization > > It could be the atomic functions failing, but more likely it's still a > DB problem. Please add this patch as well: > > Index: subversion/libsvn_subr/atomic.c > =================================================================== > --- subversion/libsvn_subr/atomic.c (revision 1202695) > +++ subversion/libsvn_subr/atomic.c (working copy) > @@ -57,8 +57,7 @@ > SVN_ATOMIC_INIT_FAILED, > SVN_ATOMIC_START_INIT); > #endif > - return svn_error_create(SVN_ERR_ATOMIC_INIT_FAILURE, err, > - "Couldn't perform atomic initialization"); > + return err; > } > svn_atomic_cas(global_status, > SVN_ATOMIC_INITIALIZED,
No change (same error). But it seems it's not this error that is triggered; it's the one a few lines down (I changed the error message to detect it): #if APR_HAS_THREADS /* Wait for whichever thread is performing initialization to finish. */ /* XXX FIXME: Should we have a maximum wait here, like we have in the Windows file IO spinner? */ else while (status != SVN_ATOMIC_INITIALIZED) { if (status == SVN_ATOMIC_INIT_FAILED) return svn_error_create(SVN_ERR_ATOMIC_INIT_FAILURE, NULL, "Couldn't perform atomic initialization");