On Thu, Jan 25, 2018 at 11:14 AM, Bill Huang-黃靖翔
I (Johan Corveleyn) wrote:
>> 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.
> May I know how do I setting it ? which file can I adjust ?
> I think my SVN server is default setting, because I do not have adjust any setting.
> And my server is physical machine Dell-R230 and free space is 1.4T , so I think diskspace is normal
> Attachments for my settings and server status
> And I just setting attachments file 02 and 03
> May I know have any more setting about SVN how can I try to setting it
I'm not talking about a setting in SVN. I'm talking about the
filesystem on which the svn backend (/var/lib/svn/0_IT_test/Bill/db)
is stored. That's /dev/sda1 if I read your screenshots correctly. Is
that filesystem capable of storing such large files?
Okay, so it has enough diskspace, and it's a local disk. What is the
type of the filesystem? I think 'mount' should show you that. Maybe
you can perform a couple of tests outside of SVN, to just test the
disk? For instance, try to create a file of 10 GB (with 'dd' or
something), then 20 GB, 50 GB (don't forget to clean them up again
I'm also wondering whether "write-caching" could play a role here.
Perhaps you can take a look and see if disabling it fixes the problem.
See for example these articles:
(I'm just guessing here -- not sure if it's related and if it's the
way to go -- but maybe you can eliminate this by trying it out)
That said, I'm not very proficient in Ubuntu or Linux in general.
Maybe someone else on this list can help more.
P.S.: one of your screenshots contained a visible password. I strongly
suggest you change that, since this is a public and archived
Received on 2018-01-25 20:29:58 CET