EWF CF disk properties report wrong free space

[Mark K Vallevand]

We are using EWF protected NTFS compressed 512 mb Compact Flash as our boot
device. There is no swap file, obviously. We are testing with SP2. We've
noticed that if you right-click on the C: drive and look at the properties,
there is very little free space available. But, if you explore the C: drive
and select all the files and directories in the root, then right-click and
look at the properties, the space used is correct. If you commit and
restart, usually the sizes reported by these two methods will be about the
same. But, after a while, the C: drive properties again shows a full disk.
The full disk popup is popping up, too. But, the disk is not full.

Any ideas?

We have some new programs that have memory leaks. If memory usage grows to
the point where it might effect EWF memory allocation, could this cause the
false disk space usage? It doesn't look like our leaking programs are using
that much memory when we've seen the disk space problem. But, it is the one
thing that I could think of that might be related.

 

[KM]

Mark,

A couple of quick questions if you don't mind:
- Do you see the same wrong free disk space report if you have EWF disabled?
- What GetFreeDiskSpace[Ex] API returns [reports] with EWF enabled, disabled?

 

[Mark K Vallevand]

1) Usually don't run without EWF enabled. Since this problem is not
directly reproducible, I'm not sure I want to run with EWF disabled on CF
for any period of time.
2) I'll need to whip up a quick program.

--
Regards.
Mark K Vallevand

Mark,

A couple of quick questions if you don't mind:
- Do you see the same wrong free disk space report if you have EWF
disabled?
- What GetFreeDiskSpace[Ex] API returns [reports] with EWF enabled,
disabled?

--
Regards,
KM, BSquare Corp.

We are using EWF protected NTFS compressed 512 mb Compact Flash as our
boot
device. There is no swap file, obviously. We are testing with SP2.
We've
noticed that if you right-click on the C: drive and look at the
properties,
there is very little free space available. But, if you explore the C:
drive
and select all the files and directories in the root, then right-click
and
look at the properties, the space used is correct. If you commit and
restart, usually the sizes reported by these two methods will be about
the
same. But, after a while, the C: drive properties again shows a full
disk.
The full disk popup is popping up, too. But, the disk is not full.

Any ideas?

We have some new programs that have memory leaks. If memory usage grows
to
the point where it might effect EWF memory allocation, could this cause
the
false disk space usage? It doesn't look like our leaking programs are
using
that much memory when we've seen the disk space problem. But, it is the
one
thing that I could think of that might be related.

 

[KM]

Mark,

1) This was only for testing purposes since you mentioned you suspected the problem was related to EWF memory allocation.
Disabling EWF will give you more test data for the issue.

--
Regards,
KM, BSquare Corp.

1) Usually don't run without EWF enabled. Since this problem is not
directly reproducible, I'm not sure I want to run with EWF disabled on CF
for any period of time.
2) I'll need to whip up a quick program.

--
Regards.
Mark K Vallevand

Mark,

A couple of quick questions if you don't mind:
- Do you see the same wrong free disk space report if you have EWF
disabled?
- What GetFreeDiskSpace[Ex] API returns [reports] with EWF enabled,
disabled?

--
Regards,
KM, BSquare Corp.

We are using EWF protected NTFS compressed 512 mb Compact Flash as our
boot
device. There is no swap file, obviously. We are testing with SP2.
We've
noticed that if you right-click on the C: drive and look at the
properties,
there is very little free space available. But, if you explore the C:
drive
and select all the files and directories in the root, then right-click
and
look at the properties, the space used is correct. If you commit and
restart, usually the sizes reported by these two methods will be about
the
same. But, after a while, the C: drive properties again shows a full
disk.
The full disk popup is popping up, too. But, the disk is not full.

Any ideas?

We have some new programs that have memory leaks. If memory usage grows
to
the point where it might effect EWF memory allocation, could this cause
the
false disk space usage? It doesn't look like our leaking programs are
using
that much memory when we've seen the disk space problem. But, it is the
one
thing that I could think of that might be related.

 

[Mark K Vallevand]

Yes. At this point it is about collecting test data for the issue. Clues
for the mystery. I was hoping someone had seen a similar problem and had an
answer.

--
Regards.
Mark K Vallevand

Mark,

1) This was only for testing purposes since you mentioned you suspected
the problem was related to EWF memory allocation.
Disabling EWF will give you more test data for the issue.

--
Regards,
KM, BSquare Corp.

1) Usually don't run without EWF enabled. Since this problem is not
directly reproducible, I'm not sure I want to run with EWF disabled on CF
for any period of time.
2) I'll need to whip up a quick program.

--
Regards.
Mark K Vallevand

Mark,

A couple of quick questions if you don't mind:
- Do you see the same wrong free disk space report if you have EWF
disabled?
- What GetFreeDiskSpace[Ex] API returns [reports] with EWF enabled,
disabled?

--
Regards,
KM, BSquare Corp.


We are using EWF protected NTFS compressed 512 mb Compact Flash as our
boot
device. There is no swap file, obviously. We are testing with SP2.
We've
noticed that if you right-click on the C: drive and look at the
properties,
there is very little free space available. But, if you explore the C:
drive
and select all the files and directories in the root, then right-click
and
look at the properties, the space used is correct. If you commit and
restart, usually the sizes reported by these two methods will be about
the
same. But, after a while, the C: drive properties again shows a full
disk.
The full disk popup is popping up, too. But, the disk is not full.

Any ideas?

We have some new programs that have memory leaks. If memory usage
grows
to
the point where it might effect EWF memory allocation, could this
cause
the
false disk space usage? It doesn't look like our leaking programs are
using
that much memory when we've seen the disk space problem. But, it is
the
one
thing that I could think of that might be related.