On Tue, May 9, 2023 at 7:45 PM Bo Berglund <bo.bergl...@gmail.com> wrote:
>
> I have an svn server running as a backup system on an Ubuntu 20.04.6 LTS 
> SERVER.
>
> $ svn --version
> svn, version 1.13.0 (r1867053)
>    compiled May 12 2022, 20:47:08 on x86_64-pc-linux-gnu
>
> Today after returning from a 2-week trip I discovered that the Ubuntu server 
> had
> run out of disk space on / and could not create files of various kinds...
>
> After I investigated the situation it turns out that
> /var/lib/svn/pc/db/txn-protorevs alone uses up 11.9 GB!

These are "dead" or "stale" uncommitted transactions[1]. You can use
`svnadmin lstxns`[2] to list them and `svnadmin rmtxns`[3] to remove
them. The first link has several helpful hints.

[1]: 
https://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.diskspace.deadtxns
[2]: https://svnbook.red-bean.com/nightly/en/svn.ref.svnadmin.c.lstxns.html
[3]: https://svnbook.red-bean.com/nightly/en/svn.ref.svnadmin.c.rmtxns.html


>
> I don't know if the system was close to full when I went on the trip but it is
> now...
>
> But the latest commits to the /var/lib/svn/pc.. was about a month ago so I
> cannot understand what has happened.
>
> So on this system svn is installed with its data in the default location
> /var/lib/svn/...
>
> What can I do now to make it operational again?
> Can I move the data to a different disk partition or something like that?
> But how would that work concerning the svn operations?
>
> The drive situation is like this:
>
> $ df -h
> Filesystem           Size  Used Avail Use% Mounted on
> udev                 6.8G     0  6.8G   0% /dev
> tmpfs                1.4G  3.6M  1.4G   1% /run
> /dev/nvme0n1p6        30G   28G     0 100% /   <==== FULL!!
> tmpfs                6.9G     0  6.9G   0% /dev/shm
> tmpfs                5.0M     0  5.0M   0% /run/lock
> tmpfs                6.9G     0  6.9G   0% /sys/fs/cgroup
> /dev/nvme0n1p8       259G  216G   31G  88% /home
> /dev/loop1           117M  117M     0 100% /snap/core/14784
> /dev/nvme0n1p1       256M   34M  223M  14% /boot/efi
> /dev/nvme0n1p7        79G   56M   75G   1% /home/bosse/www/MSNBC/data
> /dev/loop3           117M  117M     0 100% /snap/core/14946
> /dev/loop4            92M   92M     0 100% /snap/lxd/24061
> /dev/loop5            64M   64M     0 100% /snap/core20/1852
> /dev/loop6            92M   92M     0 100% /snap/lxd/23991
> /dev/loop0           9.7M  9.7M     0 100% /snap/canonical-livepatch/202
> /dev/loop7           9.7M  9.7M     0 100% /snap/canonical-livepatch/209
> /dev/loop8            64M   64M     0 100% /snap/core20/1879
> tmpfs                1.4G     0  1.4G   0% /run/user/1000
>
> And using the ncdu utitility:
>
> --- /var/lib/svn ------------------------
>                          /..
>    13.2 GiB [##########] /pc
>     1.9 GiB [#         ] /marketing
>   686.9 MiB [          ] /eng
>   402.6 MiB [          ] /pcb
>   342.2 MiB [          ] /cmp
>   335.2 MiB [          ] /appdev
>   258.2 MiB [          ] /web
>   238.3 MiB [          ] /hw
>   236.7 MiB [          ] /bosse
>   170.5 MiB [          ] /ei
>    84.3 MiB [          ] /newprod
>   300.0 KiB [          ] /private
>
> --- /var/lib/svn/pc ----------------------
>                          /..
>    13.2 GiB [##########] /db
>    40.0 KiB [          ] /hooks
>    20.0 KiB [          ] /conf
>    12.0 KiB [          ] /locks
>     4.0 KiB [          ]  README.txt
>     4.0 KiB [          ]  format
>
>
> Any ideas & suggestions welcome....
>
>
> --
> Bo Berglund
> Developer in Sweden
>


--
With best regards,
Pavel Lyalyakin
VisualSVN Team

Reply via email to