'I/O bad request chunk' error message in online log
Posted in 2003
Topics: Storage & Space Management, Logging & Checkpoints
Hi All - Last night I manually shutdown and brought up the database. I verified it was online before going home. This morning, I have discovered these error messages in my production environment. Does anyone know what's causing them? How critical are they? How can I fix them? Thanks for any insight you can share. - Jane Vohden, Fairbanks North Star Borough ******************************* 19:23:46 Dataskip is now OFF for all dbspaces 19:23:46 Checkpoint Completed: duration was 0 seconds. 19:23:46 Checkpoint loguniq 194, logpos 0xbfb018 19:23:46 Maximum server connections 0 19:23:46 On-Line Mode 19:41:26 I/O bad request chunk 0, pagenum 7780, pagecnt 1 19:41:26 I/O bad request chunk 0, pagenum 7812, pagecnt 1 19:41:26 I/O bad request chunk 0, pagenum 7844, pagecnt 1 19:41:27 I/O bad request chunk 0, pagenum 7876, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 56, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 88, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 120, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 152, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 184, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 216, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 248, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 280, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 312, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 344, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 376, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 408, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 440, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 472, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 504, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 536, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 568, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 600, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 632, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 664, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 696, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 728, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 760, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 8, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 40, pagecnt 1 19:43:23 I/O bad request chunk 0, pagenum 72, pagecnt 1 Mon Jun 9 07:11:15 2003 07:11:15 Fuzzy Checkpoint Completed: duration was 0 seconds, 1 buffers not flu shed.
FYI:
Here is what Informix had to say about those messages. No big deal.
Thank you to those of you who responded. - Jane
-------------------------------------------
Here is the problem. This is cosmetic only, does not seem to cause any
problems other than fill the message file.
Bug: 153029 ONUNLOAD REPORTS "I/O BAD REQUEST CHUNK 0, PAGENUM XXX,
PAGECNT 1" IN ONLINE.LOG
Date: 2001-09-21 Category: ONUTILS
Component: ONUNLOAD ONLINE UNLOAD UTILITY
Description:
Running onunload for a database or for some tables in that database
results in errors in the message file like "I/O bad request chunk 0,
pagenum xxx, pagecnt 1" (see online.log below).
The first 'pagenum' reported for a specific table is the same as the
number of pages allocated for that table, so it seems the onunload is
trying to read pages past the last extent.
The onload with the output generated by this onunload works fine,
i.e., all the data is restored.
There are many cases reporting this problem that seems to occur only
for versions 7.31.xD1 or later.
-----Original Message-----
From: Jane Vohden [mailto:jvohden@co.fairbanks.ak.us]
Sent: Monday, June 09, 2003 2:33 PM
To: ids@iiug.org
Subject: 'I/O bad request chunk' error message in online log [1306]
Hi All -
Last night I manually shutdown and brought up the database. I verified it
was online before going home. This morning, I have discovered these error
messages in my production environment.
Does anyone know what's causing them? How critical are they? How can I fix
them?
Thanks for any insight you can share. - Jane Vohden, Fairbanks North Star
Borough
*******************************
19:23:46 Dataskip is now OFF for all dbspaces
19:23:46 Checkpoint Completed: duration was 0 seconds.
19:23:46 Checkpoint loguniq 194, logpos 0xbfb018
19:23:46 Maximum server connections 0
19:23:46 On-Line Mode
19:41:26 I/O bad request chunk 0, pagenum 7780, pagecnt 1
19:41:26 I/O bad request chunk 0, pagenum 7812, pagecnt 1
19:41:26 I/O bad request chunk 0, pagenum 7844, pagecnt 1
19:41:27 I/O bad request chunk 0, pagenum 7876, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 56, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 88, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 120, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 152, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 184, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 216, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 248, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 280, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 312, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 344, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 376, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 408, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 440, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 472, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 504, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 536, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 568, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 600, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 632, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 664, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 696, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 728, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 760, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 8, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 40, pagecnt 1
19:43:23 I/O bad request chunk 0, pagenum 72, pagecnt 1
Mon Jun 9 07:11:15 2003
07:11:15 Fuzzy Checkpoint Completed: duration was 0 seconds, 1 buffers not
flu
shed.