Bkiowrite:insufficient Disk Space During Write

[durgaprasad1538]

Hi All,

We faced today database shutdown due to insufficient disk space this information we got from database log file(already i attached log file).in log file it mentioning due to
bkioWrite:Insufficient disk space during write, fd 13, len 16384, offset 204816, file /data/oe/bi/iCABS.b3.When we checked from server side there is no disk space issue still we have 26 gb left.

Kindly help on this.

Progress version: 11.4
PFA... error log file and cpu details..

 

[Rob Fitzpatrick]

Based on the file name and path in the 9450 error message above, the database was unable to perform a required write to the before image file, so it initiated an abnormal shutdown.

So it is possible that:

• the partition containing /data/oe/bi ran out of space, or
  
• /data/oe/bi/iCABS.b3 is a fixed-size extent and it is the last extent of the BI file, or
  
• /data/oe/bi/iCABS.b3 is a variable-size extent that reached its maximum size and could not be extended, because
  • it reached 2 GB and large file support is not enabled in the DB, or
  • it has a maximum size specified in the structure file and it reached that size, or
  • large file support is enabled and the extent reached 1 TB in size

If the BI is out of space (either logically or physically) you will need to extend it before being able to start the database again, as the database will go through crash recovery on startup and need to write more BI notes.

I'm having trouble making sense of your attached text file. It shows errors for a database with a Windows path (d:\progress\db\data\school), but the error in your message is for a Unix path.

Is there more than one database with an error?
Was the message in the text file just an example?

Please post :

• the contents of an up-to-date structure file (iCABS.st)
• the output of: proutil iCABS -C describe
• the output of: ls -l /data/oe/bi
• the output of: df -v (or df -h)

Do you have an Enterprise RDBMS or Workgroup RDBMS license?

Also, it would help others to help you if you would just post text in a text file (rather than a Word document containing a screenshot of a browser showing a spreadsheet containing a picture of text). Not everyone here has an application that can open .docx files.

 

[durgaprasad1538]

Hi Rob,

Thanks for quick update.

We enabled large file so i thinking it is not error due to variable extent flow.
available space in /data partition is 26gb.
Is this issue due to -T temp directory.

FYI.... more iCABS.pf
-db /data/oe/db/iCABS -ld core
-db /data/oe/db/iCABSReport -ld report
-db /data/oe/db/PDASyncPES
-db /data/oe/db/PDASyncHCA
-s 500
-d dmy
-yr4def
-inp 32000
-T /data/oe/ProgressTmp

PFA....

 

[jurriaan]

Is your storage by any chance attached via a network?

We had lots of these problems on our previous setup (windows server with iscsi SAN). Despite the fact that the message talks about insufficient disk space, it may just indicate some kind of hickup in the network. Very frustrating, since it's hard to reproduce and is able to destroy/corrupt your database (we had to restore from backup + after-image once, because of this). Corporate IT often views the network as some kind of best effort product, where one dropped/corrupted packet is no big deal.

Progress KB - Error 9450 when restoring backup.

I wish you luck, and hope you have a tested backup/after image process running.
It disappeared here when we moved to a linux server on vmware.

 

[TomBascom]

Hi Rob,

Thanks for quick update.

We enabled large file so i thinking it is not error due to variable extent flow.
available space in /data partition is 26gb.
Is this issue due to -T temp directory.

FYI.... more iCABS.pf
-db /data/oe/db/iCABS -ld core
-db /data/oe/db/iCABSReport -ld report
-db /data/oe/db/PDASyncPES
-db /data/oe/db/PDASyncHCA
-s 500
-d dmy
-yr4def
-inp 32000
-T /data/oe/ProgressTmp

PFA....

When someone asks you for more information it is polite to provide the information that they asked for.

 

[TomBascom]

Always start with the first error. Do not skip ahead to some random problem.

The first error shown in your .lg file is:

(291) Insufficient disk space or Write access denied.​

Unless there are earlier errors that you have not shared this is the message that is most relevant to your problem.

Since you believe that you have more than adequate disk space available you might want to consider that this could also be a permissions or file locking error. One common source for that sort of thing in a Window's environment is virus scanning. Your system appears to be a UNIX system but that does not completely preclude someone doing something ridiculous.

Also -- just because you have lots of disk space right now does not mean that you had lots of disk space when the error occurred. It is quite possible that a very large file was created, used up all the disk space, and was then deleted. A misdirected backup might, for instance, do that sort of thing. Unless you have "df" output from the time period when the problem occurred there is no special reason to think that the Progress message is wrong about being out of disk space.

 

[durgaprasad1538]

today also we faced the same issue. We are able to figure out what the issue.user running program to pull data due to this create a large file used up the disk space. After that it starts shut downing databases.

Cause:Application code error.