"Daniel Shahaf" <d.s_at_daniel.shahaf.name> writes:
> Blair's "post-commit FS processing" work (aka: svn_fs_commit_txn()
> returns an error but also returns a non-SVN_INVALID_REVNUM revision
> number) was backported to 1.6.17, but is not in 1.6.16 which svn.a.o
> runs?
>
> grep -2w svn_fs_commit_txn
> https://svn.apache.org/repos/asf/subversion/tags/1.6.16/subversion/libsvn_repos/fs-wrap.c
> grep -2w svn_fs_commit_txn
> https://svn.apache.org/repos/asf/subversion/tags/1.6.16/subversion/libsvn_repos/fs-wrap.c
>
> aka "I think it's fixed by 1.6.17 on the server".
>
> On Wed, 20 Jul 2011 16:06 -0400, "C. Michael Pilato"
> <cmpilato_at_collab.net> wrote:
>> I committed r1148918 a few minutes ago, and when I did, I saw this:
>>
>> $ svn ci subversion/ -F ~/log_message.txt Sending
>> subversion/libsvn_ra_local/ra_plugin.c Transmitting file data .
>> subversion/svn/commit-cmd.c:181: (apr_err=200030)
>> subversion/libsvn_client/commit.c:852: (apr_err=200030)
>> subversion/libsvn_client/commit.c:852: (apr_err=200030) svn:
>> E200030: Commit failed (details follow):
>> subversion/libsvn_ra_serf/commit.c:2252: (apr_err=200030)
>> subversion/libsvn_ra_serf/commit.c:2252: (apr_err=200030)
>> subversion/libsvn_ra_serf/commit.c:2252: (apr_err=200030)
>> subversion/libsvn_ra_serf/util.c:763: (apr_err=200030)
>> subversion/libsvn_ra_serf/util.c:1978: (apr_err=200030)
>> subversion/libsvn_ra_serf/util.c:1978: (apr_err=200030)
>> subversion/libsvn_ra_serf/util.c:909: (apr_err=200030) svn: E200030:
>> database is locked $
It would have been the SQLite used by post-commit rep-sharing that
returned the error:
http://svn.haxx.se/dev/archive-2011-06/0523.shtml
and as Daniel says the 1.6.16 server doesn't tell the client that the
commit was successful.
The SQLite error can occur when two post-commits overlap. In 1.7 the
rep-sharing code changed and the SQLite error is less likely to occur:
http://svn.haxx.se/dev/archive-2011-06/0568.shtml
--
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com
Received on 2011-07-21 10:38:28 CEST