bkioWrite:Insufficient disk space...

[pwpaton]

I've been following the other posts regarding this error message, but ours is a little different. I'm hoping someone can offer some insight. The log file entries are:

bkioWrite:Insufficient disk space during write, fd 175, len 1024, offset 22684672, file . (6091)
bkioWrite:Insufficient disk space during write, fd 175, len 1024, offset 22684672, file . (6091)
bkioWrite:Insufficient disk space during write, fd 175, len 1024, offset 22684672, file . (6091)
bkioWrite:Insufficient disk space during write, fd 175, len 1024, offset 22684672, file . (6091)
bkioWrite:Insufficient disk space during write, fd 175, len 1024, offset 22684672, file . (6091)
bkioWrite:Insufficient disk space during write, fd 175, len 1024, offset 22684672, file . (6091)
SYSTEM ERROR: error writing file DBIa13499, ret = -1" (6072)
Insufficient disk space or Write access denied. (291)

This is a multi-volume database with 150 fixed length extents and no variable length extent. We are currently in extent 89. The BI file is currently stable at 457965568 bytes. We have a handle on excessive BI file growth problems and have been able to keep the BI size in this area, although we have a monitoring program that will shut the database down if it reaches 950MB. The filesystem is currently at 75% with 6759180 available. I can't see where we're out of disk space. Also, the filename is missing in the error message. Is there a way to link the file descriptor (175) to the physical file? The database did not shut down. Everything appears to be OK. The errors appeared only once early this morning. Should I wait and see if it happens again (shudder) or is a dump and load in order?

Can anyone tell me what might be happening here?

Thanks, Patrick

 

[Chris Kelleher]

Actually the problems weren't writing the the database or before-image file, which is very good. It looks like for some reason it ran out of disk space when writing to a temporary file, "DBIa13499" which grew to a very large size.

 

[Unregistered]

Hi

Check where your putting the progress temporary files. Progress writes scratch files for such things as temp tables. If you don't specify -T on your client session, the temporary files go into the home directory of the user that started the progress app.

Its failing to write these files because the file system where the progress session is trying to write to is full.

Hope this helps,
Andrew Fong