TeraByte Unlimited

In PHYLOCK settings, "Use Disk Storage" is checked.

The backup is for drive C only. Drive C has 34G free on a 100G disk.

CHKDSK report no problems.

What other reasons could cause PHYlock to attempt to use RAM instead of disk?

I have 4G of RAM on this WIn7 32-bit system. PHYlock RAM Cache size is 10240 K bytes (10Mbyte). Is there any reason I should not just raise RAM cache by a factor of 10X to 100Mbytes? Firefox normally runs at 200Mbytes of RAM, so maybe IFW should get similar.

On the other hand I get error messages like "[11/02/2012 1:00:19 pm] Unable to start PHYLock for drive C:
You may need to reduce the cache size. ".


Under what circumstances is the cache too big?

On Sun, 18 Nov 2012 15:25:03 PST, just as I was about to take a herb,
timg11 disturbed my reverie and wrote:

>What other reasons could cause PHYlock to attempt to use RAM instead of disk?

I have noticed, that on occasion, PHYLock will use one or the other. I
have not paid any attention to this as the backup always completes
successfully.
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose whether or not
to dance in the puddles (Jewish proverb).

you'd have to run /logl:50 then email the last section/run of the ifw.log
file then we could tell you why.

However, you may want to run chkdsk /f on the drive.

"timg11" wrote in message news:[email protected]...

In PHYLOCK settings, "Use Disk Storage" is checked.

The backup is for drive C only. Drive C has 34G free on a 100G disk.

CHKDSK report no problems.

What other reasons could cause PHYlock to attempt to use RAM instead of
disk?

I have 4G of RAM on this WIn7 32-bit system. PHYlock RAM Cache size is
10240 K bytes (10Mbyte). Is there any reason I should not just raise RAM
cache by a factor of 10X to 100Mbytes? Firefox normally runs at 200Mbytes
of RAM, so maybe IFW should get similar.

On the other hand I get error messages like "[11/02/2012 1:00:19 pm] Unable
to start PHYLock for drive C:
You may need to reduce the cache size. ".


Under what circumstances is the cache too big?

I'll try /logn:50.

BTW - I wasn't sure how big /logn:50 would make the log file, so I thought I'd add /logmax to limit it to 10Mbytes or so.
However the ifw_en_manual does not specify what units are used for "n"... Bytes? Kbytes? Mbytes?

/logmax:n
LogMaxSize=n
Ensures the log file doesn't grow beyond the size n given. Once n is reached the data from the top of the file is purged. Because of this, you typically don't want a large n value.
Default if omitted: There is no size limit on the log file.

I ran CHKDSK /F on a reboot cycle. No problems found.

/logl:50 (L not N) .

"timg11" wrote in message news:[email protected]...

I'll try /logn:50.

BTW - I wasn't sure how big /logn:50 would make the log file, so I thought
I'd add /logmax to limit it to 10Mbytes or so.
However the ifw_en_manual does not specify what units are used for "n"...
Bytes? Kbytes? Mbytes?

/logmax:n
LogMaxSize=n
Ensures the log file doesn't grow beyond the size n given. Once n is reached
the data from the top of the file is purged. Because of this, you typically
don't want a large n value.
Default if omitted: There is no size limit on the log file.

Results with /logl:50 are below. Where do I find an interpretation of all the codes?

[11/21/2012 6:20:36 am] /b /un /d:?C: /f:H:\IMAGES\MARS\Auto7\MARS7C.TBI /max:640MiB /vb /mf /logl:50
[11/21/2012 6:20:37 am] Image for Windows 2.77 (GUI)
[11/21/2012 6:20:37 am] Starting ...
imagew.exe /b /un /d:w0@0x89 /f:"H:\IMAGES\MARS\Auto7\MARS7C" /max:640MiB /vb
[11/21/2012 6:20:39 am] PHYLock is waiting for drive writing to stop ...
[11/21/2012 6:20:39 am] DLD
[11/21/2012 6:20:39 am] FVMS
[11/21/2012 6:20:39 am] BSFN
[11/21/2012 6:20:39 am] COV
[11/21/2012 6:20:39 am] GNR
[11/21/2012 6:20:48 am] DVTS NR:5237
[11/21/2012 6:20:48 am] SII VF
[11/21/2012 6:20:48 am] SSR
[11/21/2012 6:20:48 am] WLS
[11/21/2012 6:21:24 am] SH
[11/21/2012 6:21:24 am] ULV
[11/21/2012 6:21:24 am] CSF
[11/21/2012 6:21:24 am] PHYLock using drive C:
[11/21/2012 6:21:24 am] EF
[11/21/2012 6:21:24 am] FFB
[11/21/2012 6:21:24 am] FMLCN
[11/21/2012 6:21:25 am] L SVCN:0 EC:1
[11/21/2012 6:21:25 am] CH
[11/21/2012 6:21:25 am] SHTPD
[11/21/2012 6:21:25 am] SWITCH
[11/21/2012 6:21:26 am] CU
[11/21/2012 6:21:26 am] CDDB
[11/21/2012 6:21:26 am] CUC
[11/21/2012 6:21:26 am] EXIT
[11/21/2012 6:21:26 am] PHYLock Started
[11/21/2012 6:21:26 am] PHYLock Using RAM
[11/21/2012 6:21:26 am] PHYLock version 10
[11/21/2012 6:21:31 am] Backup: Drive 0 (C:) C-MARS-W7 Partition (89) 99998 MiB HPFS/NTFS
[11/21/2012 6:21:31 am] To: H:\IMAGES\MARS\Auto7\MARS7C.TBI
[11/21/2012 6:31:02 am] PHYLock Error 0002h
[11/21/2012 6:31:03 am] INFO: Total Sectors:204796620 Total Allocated:133959232
[11/21/2012 6:31:03 am] Deleting incomplete or failed backup.
[11/21/2012 6:31:03 am] Operation Completed with Error Code 204
[11/21/2012 6:31:03 am] PHYLock failed to cache all changes. Please increase the cache size in settings.
[11/21/2012 6:31:03 am] Stop

the reason is that there are too many things pending for io and after
several (50) retries (approx 1.25 seconds) it finally gives up and just uses
RAM mode. Is there some other heavy IO operation being done at the same
time you're trying to run the backup?

"timg11" wrote in message news:[email protected]...

Results with /logl:50 are below. Where do I find an interpretation of all
the codes?

[11/21/2012 6:20:36 am] /b /un /d:?C: /f:H:\IMAGES\MARS\Auto7\MARS7C.TBI
/max:640MiB /vb /mf /logl:50
[11/21/2012 6:20:37 am] Image for Windows 2.77 (GUI)
[11/21/2012 6:20:37 am] Starting ...
imagew.exe /b /un /d:w0@0x89 /f:"H:\IMAGES\MARS\Auto7\MARS7C" /max:640MiB
/vb
[11/21/2012 6:20:39 am] PHYLock is waiting for drive writing to stop ...
[11/21/2012 6:20:39 am] DLD
[11/21/2012 6:20:39 am] FVMS
[11/21/2012 6:20:39 am] BSFN
[11/21/2012 6:20:39 am] COV
[11/21/2012 6:20:39 am] GNR
[11/21/2012 6:20:48 am] DVTS NR:5237
[11/21/2012 6:20:48 am] SII VF
[11/21/2012 6:20:48 am] SSR
[11/21/2012 6:20:48 am] WLS
[11/21/2012 6:21:24 am] SH
[11/21/2012 6:21:24 am] ULV
[11/21/2012 6:21:24 am] CSF
[11/21/2012 6:21:24 am] PHYLock using drive C:
[11/21/2012 6:21:24 am] EF
[11/21/2012 6:21:24 am] FFB
[11/21/2012 6:21:24 am] FMLCN
[11/21/2012 6:21:25 am] L SVCN:0 EC:1
[11/21/2012 6:21:25 am] CH
[11/21/2012 6:21:25 am] SHTPD
[11/21/2012 6:21:25 am] SWITCH
[11/21/2012 6:21:26 am] CU
[11/21/2012 6:21:26 am] CDDB
[11/21/2012 6:21:26 am] CUC
[11/21/2012 6:21:26 am] EXIT
[11/21/2012 6:21:26 am] PHYLock Started
[11/21/2012 6:21:26 am] PHYLock Using RAM
[11/21/2012 6:21:26 am] PHYLock version 10
[11/21/2012 6:21:31 am] Backup: Drive 0 (C:) C-MARS-W7 Partition (89) 99998
MiB HPFS/NTFS
[11/21/2012 6:21:31 am] To: H:\IMAGES\MARS\Auto7\MARS7C.TBI
[11/21/2012 6:31:02 am] PHYLock Error 0002h
[11/21/2012 6:31:03 am] INFO: Total Sectors:204796620 Total
Allocated:133959232
[11/21/2012 6:31:03 am] Deleting incomplete or failed backup.
[11/21/2012 6:31:03 am] Operation Completed with Error Code 204
[11/21/2012 6:31:03 am] PHYLock failed to cache all changes. Please
increase the cache size in settings.
[11/21/2012 6:31:03 am] Stop

The computer wakes from standby to run a scheduled task, which includes the backup.
There is a CMD file that is the action for a scheduled task that runs once a day. It performs several maintenance functions, but they are done sequentially. When it runs IFW, that should be the only process running.

This backup task has been running successfully for several years (since IFW 2 was released). It has never had a problem with IO overruns and failures until recently. That's why I thought it might have been related to something that changed with Windows Update. Or maybe something that changed with IFW in the last few months?

Nothing I can think of, you may want to try disabling IO Throttling in
settings to see if it makes a difference for you...

"timg11" wrote in message news:[email protected]...

The computer wakes from standby to run a scheduled task, which includes the
backup.
There is a CMD file that is the action for a scheduled task that runs once a
day. It performs several maintenance functions, but they are done
sequentially. When it runs IFW, that should be the only process running.

This backup task has been running successfully for several years (since IFW
2 was released). It has never had a problem with IO overruns and failures
until recently. That's why I thought it might have been related to something
that changed with Windows Update. Or maybe something that changed with IFW
in the last few months?