Menu
▾
▴
#28 Blockcache isn't scanned at start up correctly
open
nobody
None
5
2012-09-20
2008-07-12
Anonymous
No
If you put a new large blockcache in place of a old smaller one, OFF doesn't know what size the cache is.
I moved my large blockcache folder out to save it, then removed all the setting files to start new, to make OFF think I am starting new.
Start back up and the settings are now default. Let it run for a while and get 20MB of blocks.
Shut it down, delete the 20MB blockcache folder. Place the large blockcache folder where it should be and start OFF again.
It shows at the top the blockcache is only 20MB. Checking the blockcache works and it takes a long time so it's reading the larger amount. But readings don't change.
Please explain what each config file is for in a doc. Do you also have to delete or copy a config file?
So does that mean if I manually put blocks into the cache, the OFF program won't use them?
Logged In: NO
Confirmed.
1GB blockcache folder (which is under the default trim amount).
New version 19.21, no settings files of any kind, no nodes.
Says it sees only 3 blocks. Where did those blocks come from?
The 3 blocks appear on a new setup with no blockcache too.
Import of the 1GB folder goes OK (renamed so OFF doesn't know it's there) confirming the blocks are good.
Logged In: NO
If you set "check blockcache at startup" it will see the new blocks when you start the program.
Logged In: YES
user_id=1922712
Originator: NO
OFF does not check the blockcache on startup by default, because this can take a long time with large caches and some OSes and filesystem.
So if you really want to alter the cache manuelly check the "check blockcache at startup" as already suggested.
And 3 blocks are created on first startup from random data, because some blocks are needed as randomizers to store somthing.