If you are using hash to check if caching works it could be that the second run comes from built-in windows disk cache (from RAM esencially). Read from windows disk cache is not visible to Primo, only read from physical media is.
Read (for instance copy) from cached volume and check if L2Storage Write increasing after every new and never before opened (non cached already) file.
0.9.9 L2-Cache not working
Re: 0.9.9 L2-Cache not working
BTW, if you want the persistent L2 cache, please make sure that your Windows partition is not protected which means no changes can apply on Windows partition after reboot. PrimoCache have to make a flag on Windows partition to make sure that level-2 cache content is not "out of sync".
Re: 0.9.9 L2-Cache not working
It's a single boot system, so there should be no problem. Btw I asked in another topic, but did not get a reply:
What happens if the cache gets inconsistent? And is there a method that PrimoCache uses to fix it?
What happens if the cache gets inconsistent? And is there a method that PrimoCache uses to fix it?
Re: 0.9.9 L2-Cache not working
PrimoCache verifies cache state to make sure it is sync with disk source. But if L2 storage or disk source got changed "offline", cache may be out of sync. Then unexpected error may happen. You may fix it by "reset cache content" command.szucsati wrote:What happens if the cache gets inconsistent? And is there a method that PrimoCache uses to fix it?