[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9877.0. "Deferring I/O Message" by NCMAIL::YANUSC () Mon May 19 1997 14:45

    This message is also being directed to Customer Services in the event
    that it is strictly a hardware error.
    
    The Government program I manage from a sales standpoint has gotten a
    tricky problem that has not yet been rectified.  They receive a
    particular error message that causes problems generally necessitating a
    reboot, and then goes away.  Everything appears to be okay, and it then
    rears its ugly head.  The prime contractor and Digital have both been
    working on the problem, but have not resolved it yet.  I was hoping
    that someone here may have seen this already and could shed some light
    on it, since the message is being generated by the UNIX operating
    system.
    
    The error message received is: "Deferring I/O (Error -1 or Error 5)"
    
    The prime contractor was told that this means a h/w error, but no one
    has been able to shed any light on its cause or what not.  The system
    is a relatively new 2100A system running Digital UNIX 3.2D (will go to
    4.0x in September; not an option before then.)  If anyone can give any
    advice it would be appreciated.
    
    Chuck
T.RTitleUserPersonal
Name
DateLines
9877.1Get an error logNNTPD::"[email protected]"Bill DallasMon May 19 1997 17:4115
This message is a result of an I/O subsystem returning a error on an I/O
request
that could not be satisfied.  The reason for the I/O failure should be
recorded
in the error logs.

There are numerous reasons why the I/O request is failed but some are
un-recoverabled media errors, device has gone away, device fault, etc.

To find the real cause of the problem review the error log.

Regards,
Bill
[Posted by WWW Notes gateway]