L2 Cache reset debugging and recovery feature

Suggestions around PrimoCache
Post Reply
wchris
Level 1
Level 1
Posts: 4
Joined: Fri Jun 13, 2014 8:04 am

L2 Cache reset debugging and recovery feature

Post by wchris »

Hello,

I currently use primocache trial, it works well, between two L2 cache resets.

L2 Cache reset is a very good security, and I prefer this behavior to having corrupt data.

However I cannot diagnose the origin of the problem and fix it.

Maybe you could add a "debug mode" option where the L2 cache would not de deleted when detected out of sync, but instead kept and marked unusable.

Then after boot, in primocache GUI you could add a button feature to check the L2 cache blocks and compare them to the disk.

If all blocks are correct ... no cache reset, L2 cache is simply marked usable again. ( =less writes to ssd)

if differences are found, output a list of files ( or disk reserved area like FAT) where the block belongs. (maybe if I know what file I could diagnose what is causing the L2 cache resets)

You could also add a "resync" button where L2 cache blocks that are different would be updated from disk and cache could be marked usable again without rebuilding it as a whole.

thanks

Edit : Also add a log of cache resets and cache events ( yes more work :D ) Of course for each reset this log would display cache configuration, date time, and all related valuable infos.

Cheers

Additional info : I never enable defer write. I tryed both "SSD cache with read only strategy" and "SSD cache read & write" with all block sizes and various storage sizes from 2048 to max 50gb. Same result L2 cache is reset every reboot. Using version 1.01 on a windows Xp SP3 machine.

Edit : finally got the L2 cache working again.
Uninstalled primocache, did a chkdsk /f, re-installed primocache 1.01. Yesterday's cache is still here.
Note that a chkdsk /f at reboot time with cache removed but without uninstall/reinstall was not enought.
So uninstall/reinstall fixed it... maybe it makes sense to you ?
User avatar
Support
Support Team
Support Team
Posts: 3623
Joined: Sun Dec 21, 2008 2:42 am

Re: L2 Cache reset debugging and recovery feature

Post by Support »

Thanks for your information! It seems a little strange in your case. As described in our help documents, PrimoCache traces and updates flags saved in Windows registry to make sure L2 cache data is in sync. I think your issue might be related to data corruption which cannot correctly update flags.
wchris
Level 1
Level 1
Posts: 4
Joined: Fri Jun 13, 2014 8:04 am

Re: L2 Cache reset debugging and recovery feature

Post by wchris »

Hello,

Thanks for the answer.

Problem not solved. The cache resisted several reboots this morning, until II shutdown the machine.

When I power on the machine this evening, cache is reset.

I have no clue. If you could imagine a diagnostic too that could provide hints it would be usefull. Knowing what flag is wrong could provide a hint.
If you don't want to disclose flags, you could imagine a system that sends you back cache reset info like microsoft error reporting system.

Cheers

EDIT : for you I have this information

at startup event observer says

Event 1524 : Windows can not unload your classes registry file - it is in use by other applications or services. The file will be unloaded when it is no longer used.
Event 1517 : Windows saved user registry WINXP2 \ TEDDY while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer used.

  This is often caused by services running as a user account, try configuring the services to run in the local service account or network service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Can this be related ?


Also a chkdsk /f at startup says ok but event observer says :
Event 1001 : Checking file system on C:
The type of file system is NTFS.


The integrity of one of your disks needs to be checked.
You may cancel this verification, but its execution is
highly recommended.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 2 unused index entries from index $ SII of file 0x9.
Cleaning up 2 unused index entries from index $ SDH of file 0x9.
Cleaning up 2 unused security descriptors.
CHKDSK is verifying USN journal ...
Checking the USN journal completed.

 293033600 KB total disk space.
 128542920 KB in 292498 files.
    112904 KB in 16504 indexes.
         0 KB in bad sectors.
    851500 KB used by the system.
     65536 KB occupied by the log file.
 163526276 KB available on disk.

      4096 bytes in each allocation unit.
  73258400 total allocation units on disk.
  40881569 allocation units available on disk.

Internal information:
00 18 05 00 15 b7 04 00 01 65 07 00 00 00 00 00 ......... e ......
4f 08 00 00 06 00 00 00 c2 07 00 00 00 00 00 00 O. ..............
3d dc 1a 08 00 00 00 00 30 44 c0 47 01 00 00 00. = ...... 0D.G. ...
August 92 5c 5e 00 00 00 00 00 00 00 00 00 00 00 00 .. \ ^ ............
00 00 00 00 00 00 00 00 54 7b d1 bc 01 00 00 00 ........ T {......
99 9e 36 00 00 00 00 00 f8 34 07 00 92 76 04 00 .. 6 ...... 4 ... v ..
00 00 00 00 00 20 a3 a5 1e 00 00 00 78 40 00 00 ........... @ x ..

Windows has finished checking your disk.
Please wait while your computer restarts.

But my googling shows 0x9 error is a windows bug and not critical.


Any further suggestions based on this ? Can one of those events be the culprit of cache resets ? Thanks
Post Reply