Restore Points/Disk Space problem?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an XP Embedded machine in the field that has a 40 GB drive partitioned
3 ways. C:\ is 10.1 GB. D:\ is 16.2 GB. E:\ is 10.1 GB. The C:\ drive was
down to 55 MB of free space, so I did some poking around with TreeSize.

I found that there were 2 restore points. One that occurred on February 7,
a 6.9 GB restore point; and another on March 4, a 2.3 GB restore point.
There were other restore points of inconsequential size.

Based on the way System Restore points are configured on these kiosks is 12%
max, meaning they should only grow to 1.2 GB.

Is there a known SP1 incident on this? What else can/should I check. The
app logs and sys logs have rolled, but I have other kiosks that have the same
problem

The offending restore points keep dumping the a*.sys file Virtual memory is
fixed at 768 MB.

It's running Windows XP Embedded SP1, on a Pentium III 732 MHz processor,
256 MB RAM.

Has someone seen this before?
--
Slater...

Jeff

"Time is an illusion, rising from time."
 
I turned off restore points all together. At least, that is what these
registry keys are intended to do:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\SystemRestore
DisableSR
REG_DWORD
1

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sr
Start
REG_DWORD
4




--
Regards.
Mark K Vallevand (e-mail address removed)

Beer is living proof that God loves us and wants us to be happy.
- Benjamin Franklin


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
 
Jeff,

Any chance for you to verify the following registry value at your run time?
[HKLM\Software\Microsoft\Windows NT\CurrentVersion\SystemRestore\Cfg],"DiskPercent"?

Or, can you show use the content of the entire key?
 
KM,

The following are the values for the entire key:

DiskPercent = 0x0000000c (12)
MachineGuid = {91EE6FF-E52F-4539-B069-8E6E8BB50140}
RPGlobalInterval = 0x0015180 (86400)
RPLifeInterval = 0x0076a700 (7776000)
RPSessionInterval = 0x00000000 (0)

I looked at another site that had a 6 GB partion, and they had a 2.3 GB
restore point. There were 3 a[Sequential Numbered].sys files. This are
memory dumps, right? All are the same size as the pagefile.sys

There are two things I'd like to get my hands around on this issue. The
first is why these machines creating the huge restore points. The second is
why XP Embedded is not managing the deletion of the restore points in cases
where this occurs.

Our client spec will not allow us to turn off Restore Points, so that's not
an option. We may turn it off to allow it to purge these huge ones/recover
the disk space, and then enable. I need to understand whats going wrong
before I can move forward.

Any help is much appreciated.

Jeff

KM said:
Jeff,

Any chance for you to verify the following registry value at your run time?
[HKLM\Software\Microsoft\Windows NT\CurrentVersion\SystemRestore\Cfg],"DiskPercent"?

Or, can you show use the content of the entire key?

--
Regards,
KM, BSquare Corp.

I have an XP Embedded machine in the field that has a 40 GB drive partitioned
3 ways. C:\ is 10.1 GB. D:\ is 16.2 GB. E:\ is 10.1 GB. The C:\ drive was
down to 55 MB of free space, so I did some poking around with TreeSize.

I found that there were 2 restore points. One that occurred on February 7,
a 6.9 GB restore point; and another on March 4, a 2.3 GB restore point.
There were other restore points of inconsequential size.

Based on the way System Restore points are configured on these kiosks is 12%
max, meaning they should only grow to 1.2 GB.

Is there a known SP1 incident on this? What else can/should I check. The
app logs and sys logs have rolled, but I have other kiosks that have the same
problem

The offending restore points keep dumping the a*.sys file Virtual memory is
fixed at 768 MB.

It's running Windows XP Embedded SP1, on a Pentium III 732 MHz processor,
256 MB RAM.

Has someone seen this before?
--
Slater...

Jeff

"Time is an illusion, rising from time."
 
Jeff,
The following are the values for the entire key:

DiskPercent = 0x0000000c (12)
MachineGuid = {91EE6FF-E52F-4539-B069-8E6E8BB50140}
RPGlobalInterval = 0x0015180 (86400)
RPLifeInterval = 0x0076a700 (7776000)
RPSessionInterval = 0x00000000 (0)

These are defaults. Good to know.

You may also want to add DSMax value there to improve the disk space limitation for SR. See more details here:
http://support.microsoft.com/kb/295659
I looked at another site that had a 6 GB partion, and they had a 2.3 GB
restore point. There were 3 a[Sequential Numbered].sys files. This are
memory dumps, right? All are the same size as the pagefile.sys

Potentially (not to uncover the source of the problem) you can fix the issue in future by moving the pagefile to a separate small
(enough for pagefile) partition and turn off the Systemn Restore for that partition.
There are two things I'd like to get my hands around on this issue. The
first is why these machines creating the huge restore points. The second is
why XP Embedded is not managing the deletion of the restore points in cases where this occurs.

Well.. I think your RPLifeInterval is set to 90 days. After the RPs on your devices were created, did it pass 90 days?
Our client spec will not allow us to turn off Restore Points, so that's not
an option. We may turn it off to allow it to purge these huge ones/recover
the disk space, and then enable. I need to understand whats going wrong
before I can move forward.

can you check the Event Viewer Logs to see if any messages were received from SR services on broken devices?


--
Regards,
KM, BSquare Corp.


KM said:
Jeff,

Any chance for you to verify the following registry value at your run time?
[HKLM\Software\Microsoft\Windows NT\CurrentVersion\SystemRestore\Cfg],"DiskPercent"?

Or, can you show use the content of the entire key?

--
Regards,
KM, BSquare Corp.

I have an XP Embedded machine in the field that has a 40 GB drive partitioned
3 ways. C:\ is 10.1 GB. D:\ is 16.2 GB. E:\ is 10.1 GB. The C:\ drive was
down to 55 MB of free space, so I did some poking around with TreeSize.

I found that there were 2 restore points. One that occurred on February 7,
a 6.9 GB restore point; and another on March 4, a 2.3 GB restore point.
There were other restore points of inconsequential size.

Based on the way System Restore points are configured on these kiosks is 12%
max, meaning they should only grow to 1.2 GB.

Is there a known SP1 incident on this? What else can/should I check. The
app logs and sys logs have rolled, but I have other kiosks that have the same
problem

The offending restore points keep dumping the a*.sys file Virtual memory is
fixed at 768 MB.

It's running Windows XP Embedded SP1, on a Pentium III 732 MHz processor,
256 MB RAM.

Has someone seen this before?
--
Slater...

Jeff

"Time is an illusion, rising from time."
 
Back
Top