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

List:       jakarta-commons-dev
Subject:    Re: [all] commit problem
From:       Konstantin Kolinko <knst.kolinko () gmail ! com>
Date:       2012-02-16 22:37:16
Message-ID: CABzHfVk4DE=YG2sd390zf04ZRj6gNUoNPFEYV2WhCqpooZbbLA () mail ! gmail ! com
[Download RAW message or body]

2012/2/17 Thomas Neidhart <thomas.neidhart@gmail.com>:
> Dear all,
>
> when performing my last commit, I got the following error:
>
> Transmitting file data ...
> Committed revision 1245133.
>
> Warning: post commit FS processing had error:
> database is locked
>

I think it is worth reporting to users@subversion.a.o mailing list.

Links:
[1] http://subversion.tigris.org/issues/show_bug.cgi?id=3506
"Large commits tend to lock up FSFS"
[2] http://subversion.markmail.org/thread/zhz4o2d6nilptcx2
"SQLite locking and FSFS rep-sharing" thread, June 2011.

The issue 3506 is labeled as fixed in svn 1.6.12, but ASF runs
subversion 1.7 now.

>
> and afterwards a svn up gives this message:
>
> svn: A reported revision is higher than the current repository HEAD
> revision.  Perhaps the repository is out of date with respect to the
> master repository?
>

This is easy. You are in Europe. There is a large commit going in the
background. Replicating it from US to EU needs some time and the EU
mirror does not know about that last revision yet.

> Something I can do about it locally?
>

I would do an "svn up".

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

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