Disk is full error

[David (PassMark)]

Re: The 2D Frame display error after minimize.

This is in fact normal behavior. The frame (which is just DirectX term for 'image') was not displayed because the window was not visible on the screen.

I think we blocked the logging of this particular frame error in release V3.2 build 1002.

----
David
PassMark

[David (PassMark)]

Answering the disk full issue first:

The disk test in BurnInTest is designed to write and read data to / from the disk. To do this it creates a number of files on the disk. The test is designed so that the disk becomes very close to being full without being totally full. Having a totally full disk would cause the system to crash if the paging file was on the disk under test and the paging file needed to be expanded.

So in theory the disk test will stop writing new data when the disk is roughly 94% full. The exact percentage is determined by the file size value selected in the disk test preferences window.

So the error you see (disk full while writing a file) should not happen. I can only think of a few reasons why this might happen.

1/ You have disk quotas enabled on the machine
2/ For some reason the amount of free disk space being reported is not exactly correct. (Maybe the RAID controller needs to keep some spare space and doesn't allowing writing beyond a certain level?)
3/ There is another process running in the background, which is also using up disk space. So when the check for available space is done it seems like there is space available, but half way through writing the file the space has been used up by the external process.

=====
David
PassMark

[sbaker899]

Re: Disk is full error

We have been running the BurnInTest disk test's on a Windows 2000 Server machine, with a RAID 5 array and getting error's that we've not seen before on it. The error shown within BIT is as follows:

"Error writing to disk - disk is full"

As well as this, the standard Windows low disk space error is logged in the event logs. Does this indicate a problem with the system, or is it Ok for BurnInTest to be filling the C: drive up?

In addition to the problem I mentioned above, we also have another issue on the same machine, where when the 2D test windows is minimised during testing a frame display error will be reported upon every attempt. This is also something we've not seen before - is this standard behaviour?

Thanks for any response.

[Anonymous]

We have been running the BurnInTest disk test's on a Windows 2000 Server machine, with a RAID 5 array and getting error's that we've not seen before on it. The error shown within BIT is as follows:

"Error writing to disk - disk is full"

As well as this, the standard Windows low disk space error is logged in the event logs. Does this indicate a problem with the system, or is it Ok for BurnInTest to be filling the C: drive up?