HP3000-L Archives

October 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gilles Schipper <[log in to unmask]>
Reply To:
Gilles Schipper <[log in to unmask]>
Date:
Mon, 4 Oct 1999 22:56:17 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (43 lines)
The acceptable number of DISK I/O errors is zero.

In SYSDIAG's LOGTOOL, use the following:

STATUS (to see log files)
SUMMARIZE LOG=aaaa/bbbb  (where a is first log file number, b is last log
file number)
LIST LOG=aaaa/bbbb TYPE=111 LDEV=1-4,30-39 (assuming 1 thru 4 and 30 thru
39 are disk device numbers)


There should be zero such records.

However, some are more serious than others. SOFTWARE errors are less
serious than HARDWARE errors.  Any events shown will indicate which type of
I/O error occurred.


At 04:38 PM 1999-10-04 -0700, Paul H. Christidis wrote:
>Fellow Listers,
>
>What is an 'acceptable' level of 'I/O error' records in the system log files?
>
>Stan's suggestion of using the 'summarize' command of 'logtool' to
determine the
>most "popular" events being logged 'revealed' that our system log files
contain
>a rather high percentage (36%) of 'I/O error' records.  While 'Predictive',
>which runs on a nightly basis, has not reported any potential problems.
>
>Regards
>Paul H. Christidis
>
>
---------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP3000 & HP9000 System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000     Fax: 905.889.3001
Internet:  [log in to unmask]
---------------------------------------------------------------------------

ATOM RSS1 RSS2