#9 Cache trim doesn't free up diskspace

[Kevin Steen]

The cache trim process doesn't seem to be freeing up any disk space - the cache keeps on growing until the free disk space is below minimum.
Version: 0.18.10
Platform: Debian Etch

Log extract:

Sun Feb 17 12:47:49 2008: BlockCache size (2418.62 MB) exceeds maximum allowed (1901.46 MB)
Sun Feb 17 12:47:49 2008: Trimming blockcache, current size: 19349 blocks (2418.62 MB)
Sun Feb 17 12:47:49 2008: attempting to trim by: 176 blocks (22.00 MB)
Sun Feb 17 12:47:49 2008: updating block statistics...
Sun Feb 17 12:47:50 2008: MapDescriptor(): failed to get hash map.
Sun Feb 17 12:47:50 2008: Aborting.
Sun Feb 17 12:47:51 2008: MapLocalURLs() - finished mapping cache.
Sun Feb 17 12:47:51 2008: checking for unpreserved blocks...
Sun Feb 17 12:47:51 2008: Scheduled pushes for 176 blocks (22.00 MB)
Sun Feb 17 12:48:49 2008: Block push: node 1 - 134.108.47.7:23403:ph4tp1p3:0.18.10 refused downstream push, HDl: 88, HDr: 62, bucket: 64
Sun Feb 17 12:50:16 2008: Block push: node 114 - 217.81.5.56:23403:jesus (off.6x.to):0.18.10 refused downstream push, HDl: 87, HDr: 65, bucket: 75
Sun Feb 17 12:50:19 2008: Block push: node 114 - 217.81.5.56:23403:jesus (off.6x.to):0.18.10 refused downstream push, HDl: 87, HDr: 73, bucket: 75
Sun Feb 17 12:52:19 2008: Block push: node 114 - 217.81.5.56:23403:jesus (off.6x.to):0.18.10 refused downstream push, HDl: 87, HDr: 67, bucket: 75
Sun Feb 17 12:55:28 2008: Disk space below minimum - downloads suspended
Sun Feb 17 12:57:54 2008: BlockCache size (2430.12 MB) exceeds maximum allowed (1901.46 MB)
Sun Feb 17 12:57:54 2008: Another trim is currently in progress, trim aborted
Sun Feb 17 12:59:47 2008: Block push: node 114 - 217.81.5.56:23403:jesus (off.6x.to):0.18.10 refused downstream push, HDl: 87, HDr: 71, bucket: 75
Sun Feb 17 13:07:58 2008: BlockCache size (2425.38 MB) exceeds maximum allowed (1901.46 MB)
Sun Feb 17 13:07:58 2008: Another trim is currently in progress, trim aborted

[Nobody/Anonymous]

Logged In: NO

Hi

Sun Feb 17 12:47:51 2008: Scheduled pushes for 176 blocks (22.00 MB)
This message suggests that there aren't many blocks that could be trimmed at all. It can only find 22MB to trim.
Try unpreserving or deleting some URLs and maybe set trim size to a higher value e.g. 500MB

da1l6

[da1l6]

Logged In: YES
user_id=1922712
Originator: NO

Current CVS code does now include a change allowing to set priority for cache trim traffic.
Try compiling that from source or wait for the next release.

However, trim still takes some time and lots of bandwidth (each block is uploaded 3 times).

Tips:

• Pause downloads, because download speed is ofter greater then upload speed, the cache will still grow.
• Redruce bucket radius, this will reduce the number of blocks your node will have to take responsibility of.

da1l6