Fancy.cache 0.6.2 incompatible w/Win 7 Backup & Restore

[insertrealname]

Thanks for the links and suggestions, I will follow them up.

(But I won't be able to do so until late September--including further experiments to see if these errors are really Fancy.Cache's fault.)

[intika]

You'r welcome... let us know

cheers

[JimF]

I just installed FancyCache 0.6.2 two days ago, and this morning I got the following error (Windows 7 64-bit):

Log Name: System
Source: Ntfs
Date: 8/21/2011 3:45:31 AM
Event ID: 134
Task Category: (2)
Level: Warning
Keywords: Classic
User: N/A
Computer: Jim-PC
Description:
The transaction resource manager on volume \Device\HarddiskVolumeShadowCopy2 encountered an error during recovery. The resource manager will continue recovery.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Ntfs" />
<EventID Qualifiers="32772">134</EventID>
<Level>3</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-08-21T07:45:31.660671100Z" />
<EventRecordID>7387</EventRecordID>
<Channel>System</Channel>
<Computer>Jim-PC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\Device\HarddiskVolumeShadowCopy2</Data>
<Binary>1C00300002005C00020000008600048000000000020100C00000000000000000000000000000000000400000E18A32F28ECAE01192740022156B870B80F8FFFFCF4100000000000000007B01030000000300000000000000</Binary>
</EventData>
</Event>

Note the time of this error (3:45:31 AM). I have Jungle Disk set to back up my files to the servers at Rackspace at 3:45:00 AM, and it runs for about 1.5 minutes. I don't see any file corruption or any other problem, it is just an entry in the log that I have never seen before.

I have FancyCache set as follow:

[intika]

Hello JimF,

you are putting 6h for deferred write ?? !!! try first to make this value less important... if you want to make deferred write time as big as that you have to set more and more memory for cache... you can try 60 sec at first time...

are you making backup of files on c: ?

have a nice day...

[JimF]

Hello JimF,

you are putting 6h for deferred write ?? !!! try first to make this value less important... if you want to make deferred write time as big as that you have to set more and more memory for cache... you can try 60 sec at first time...

are you making backup of files on c: ?

have a nice day...

The problem does not seem to have anything to do with the latency. I have been running with 24 hours latency on another PC for several months with no problem. And on this PC there is plenty of cache free; at least 500 MB, so I don't think that will solve it either.

No, I am not making backups, but I run a distributed computing program (World Community Grid) that writes a lot to disk. Most of it just overwrites old data, so relatively little (only about 2 percent) gets written to the disk when the cache is flushed. That is why I can use a long latency, which saves wear on my SSD. That is the main purpose for my using FancyCache to begin with. But note that on the other PC, I don't use any backup software, so that is why this error message implicates a problem with the backup and FC.

[intika]

Hi Jim,

In your capture the cache is at 100 % (used cache at right 1536 - at left cache set to 1536) it's why i talk about that...

Any way i have no idea... support will tell

[JimF]

In your capture the cache is at 100 % (used cache at right 1536 - at left cache set to 1536) it's why i talk about that...

The one on the right ("Status") just reports the same thing shown on the left ("Configuration") after you have restarted the cache after a change. You have to look in the "Performance Monitor" to see what is really going on at the moment. I think it is the same bug that others are reporting, since the error message seems to be the same, though it is not really a problem for me thus far.

[intika]

ohh sorry i did not pay attention... you are right real used value are on the monitor...
as i say support will tell later

insertrealname, have you made some tests ?

[Support]

The issue that incompatible with win7 Backup & Restore will be fixed in the next version.

Regarding the possible NTFS corruption or warning, so far we haven't reproduced the issue yet. We'll keep testing on this issue.

Thank you, guys.

[Support]

The issue that incompatible with Windows 7 Backup & Restore has been fixed in version 0.7.0