inode usage: when to delete transactions files after committing failed

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

inode usage: when to delete transactions files after committing failed

Keva-Slient

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.

------------------
.........
Vanity...My favourite sin.
    --<<The Devil's Advocate>>
 
Reply | Threaded
Open this post in threaded view
|

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

Johan Corveleyn-3
On Thu, Jan 4, 2018 at 3:33 AM, Keva-Slient <[hidden email]> 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:
http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.diskspace.deadtxns

--
Johan
Reply | Threaded
Open this post in threaded view
|

回复: inode usage: when to delete transactions files after committing failed

Keva-Slient

thank you very much, i will have a loot at this.
------------------
.........
Vanity...My favourite sin.
    --<<The Devil's Advocate>>
 


------------------ 原始邮件 ------------------
发件人: "Johan Corveleyn";<[hidden email]>;
发送时间: 2018年1月4日(星期四) 下午4:56
收件人: "Keva-Slient"<[hidden email]>;
抄送: "users"<[hidden email]>;
主题: Re: inode usage: when to delete transactions files after committing failed

On Thu, Jan 4, 2018 at 3:33 AM, Keva-Slient <[hidden email]> 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:
http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.diskspace.deadtxns

--
Johan