Hi Bill,
Please use "reply all" to keep the mailinglist in cc, so others can
help as well.
And as I said before, we prefer "bottom-posting" on this list, or
inline replying (if at all possible). Anyway, some more info below ...
On Thu, Jan 25, 2018 at 3:10 AM, Bill Huang-黃靖翔
<Bill.Huang_at_unizyx.com.tw> wrote:
> Dear Johan
>
>
> Thanks for your relpy !
>
> I create a new SVN server and create new repository
> But commit file still have a problem
>
> May I know SVN commit file have any limit ?
> Such as commit file size total can't exceed 10GB ?
>
> Because when I commit less file (total size 1G) it can normal.
> But when commit a lot of file (total size about 50GB) it will fail
>
> Error message as I submitted to you before
For context, I'm pasting the error messages from the previous mail:
[Thu Jan 18 18:59:47.799933 2018] Could not MERGE resource
"/svn/0_IT_test/Bill/!svn/txn/4-e" into "/svn/0_IT_test/Bill". [500,
#0]
[Thu Jan 18 18:59:47.799948 2018] An error occurred while
committing the transaction. [500, #160014]
[Thu Jan 18 18:59:47.799950 2018] Reference to non-existent node
'_2j3j.0.t4-e' in filesystem '/var/lib/svn/0_IT_test/Bill/db' [500,
#160014]
You also said:
>> > SVN server is ubuntu 16.04
>> > SVN version is 1.9.3
Good thing that you reproduced it on a new, clean repository. This new
repository is on a similar environment, with the same SVN server
version?
Since you mentioned that the error only occurs if the total size of
the commit gets large, the first suspect is the back-end filesystem. I
think SVN internally has no (practical) limit on the total size of the
commit. But in the end a commit becomes a single "rev" file on the
back-end. The size of that rev file depends on the incoming files, and
compression and deltification that the server applies.
In the error message above that back-end filesystem is on
'/var/lib/svn/0_IT_test/Bill/db'. If you take a look there, you'll see
directories 'revs', 'transactions', 'txn-protorevs', ... Is there a
maximum file size limit on the level of the filesystem there? Is there
enough diskspace? Is there anything special with the way you set
things up? Are these local filesystems, or networked filesystems
connected via NFS or SMB? Did you perhaps mount 'revs' and
'transactions' from different filesystems? Any special write-caching
options that could be playing a role here? ... Those are all potential
areas for further investigation.
--
Johan
Received on 2018-01-25 10:22:58 CET