[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: inode usage: when to delete transactions files after committing failed

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Thu, 4 Jan 2018 09:56:00 +0100

On Thu, Jan 4, 2018 at 3:33 AM, Keva-Slient <356730059_at_qq.com> wrote:
> there are many transactions files after committing failed in my svn server.
> they cost lots of inodes.
> when and how can i delete them?
> i've found out that server will generate new transaction dir
> xx/db/transactions/[0-9]+\-[0-9]+.txn dir after each failed committing.
> any tool can delete them when server running? i dont want to delete the txn
> dir which is in using.

You can use the tools 'svnadmin lstxns' and 'svnadmin rmtxns' for that.

The 'lstxns' subcommand supports a '-r REV' argument, which will then
skip all transactions that are based on a more recent revision than
REV (in other words: you will only see transactions that have been
started before REV). As the help text for 'svnadmin lstxns' says:
"Transactions with base revisions much older than HEAD are likely to
have been abandonded and are candidates to be removed."

If you want, you can also use the various 'svnlook' subcommands to
inspect the transaction.

See this section of the book for some more background info:

Received on 2018-01-04 09:56:30 CET

This is an archived mail posted to the Subversion Users mailing list.