Re: inodes usage of svn server

On Tue, 2 Jan 2018 22:20:13 -0500, Nico Kadel-Garcia
<nkadel_at_gmail.com> wrote:

>On Tue, Jan 2, 2018 at 9:37 PM, Keva-Slient <356730059_at_qq.com> wrote:
>>
>> inodes usage of my svn server grows up quickly as repositories commits
>> increasing.
>> there are many reversion files in xx/db/revs/[0-9]+/[0-9]+.
>
>There is "svnadmin pack", which needs to run on the Subversion
>repository server.
>

Is this a one-time cleanup operation or does it need to be executed
regularly? I.e. does running "svnadmin pack" on the repo consolidate
the many files into a smaller number of big files and set some
repository property such that it will work that way in the future?

This is what I found in svnbook 1.7 page 178:

"By concatenating all the files of a completed
shard into a single “pack” file and then removing the original
per-revision files, svnadmin pack reduces the file count within a
given shard down to just a single file."

and

"Repacking packed shards is legal, but will have no effect on the disk
usage of the repository."

What exactly is a "shard"?
Is it one of the numerical directories each containing exactly 1000
files?

If so the "shard" storage on my repos seem to only cost at most 4%
extra disk space compared to using a single file (comparing file sizes
against disk usage).

Or will compression of the "svnadmin pack" operation make the combined
size of the files even smaller? I.e. it does not only save unused file
allocation space but actually packs the content even better?

-- 
Bo Berglund
Developer in Sweden