cancel
Showing results for 
Search instead for 
Did you mean: 

How to check for I/O errors

SOLVED
Go to solution
C_V
Frequent Advisor

How to check for I/O errors

Hey guys how do you check for I/O errors, can iostat provide that info?
11 REPLIES
RAC_1
Honored Contributor

Re: How to check for I/O errors

iostat wont show that.

look at syslog.log, dmesg, stm, ems!!!!
There is no substitute to HARDWORK
Steven E. Protter
Exalted Contributor

Re: How to check for I/O errors

Shalom,

/var/adm/syslog/syslog.log

dmesg as noted above.

mstm cstm or xstm has tools to let you check all disks and will report errors.

xstm runs in X, usually under CDE.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Jaime Bolanos Rojas.
Honored Contributor

Re: How to check for I/O errors

well you already got your answer, but usually people ask for their i/o error first, why are you suspecting of I/O errors?

Regards,

Jaime.
Work hard when the need comes out.
C_V
Frequent Advisor

Re: How to check for I/O errors

Because of this error i received vmunix: msgcnt 23 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 480 and a documents the Veritas file system admin guide suggests that it is related to a I/O... i have use cstm before but im not good at it. what is that tool in cstm that will show the I/O error...
C_V
Frequent Advisor

Re: How to check for I/O errors

Also who do i determine in syslog/dmesg if its a I/O error
C_V
Frequent Advisor

Re: How to check for I/O errors

This is the content of my dmesg:


LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1.
LVM: Restored PV 0 to VG 1.
msgcnt 1 vxfs: mesg 037: vx_metaioerr - /dev/vg_viper/lvol3 file system meta data read error
msgcnt 2 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 480
msgcnt 3 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 481
msgcnt 4 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 482
msgcnt 5 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 480
msgcnt 6 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 481
msgcnt 7 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 482
msgcnt 8 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 480
msgcnt 9 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 481
msgcnt 10 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 482
msgcnt 11 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 480
msgcnt 12 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 481
msgcnt 13 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 482
msgcnt 14 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 480
msgcnt 15 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 481
msgcnt 16 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 482
msgcnt 17 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 480
msgcnt 18 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 481
msgcnt 19 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 482
msgcnt 20 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 480
msgcnt 21 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 481
msgcnt 22 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 482
msgcnt 23 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 480
msgcnt 24 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 481
msgcnt 25 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 482
msgcnt 26 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 480
msgcnt 27 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 481
msgcnt 28 vxfs: mesg 016: vx_ilisterr - /opt/weblogic file system error reading inode 482
Bill Hassell
Honored Contributor
Solution

Re: How to check for I/O errors

dmesg is telling you that oyu have a bad disk or at possibly a bad connection. You'll see some of these error messages in syslog too.


Bill Hassell, sysadmin
C_V
Frequent Advisor

Re: How to check for I/O errors

how do you resolve this or verify it?
Bill Hassell
Honored Contributor

Re: How to check for I/O errors

Call HP for service. Attached is a manual that discusses replacing a disk in general terms but it would be difficult if you're not familiar with HP-UX and the disk hardware.



Bill Hassell, sysadmin
Joelmel Roche
Valued Contributor

Re: How to check for I/O errors


hi CV,

base in dmesg logs

LVM: Recovered Path (device 0x1f030000) to PV 0 in VG 1

1f030000 - /dev/dsk/c3t0d0 - encounter a I/O errors. this disk is belong to VG01

check in ioscan and diskinfo the disk.

regards,

joelmel



James R. Ferguson
Acclaimed Contributor

Re: How to check for I/O errors

Hi:

An updated version of the the "When Good Disks Go Bad" can always be found in the HP-UX v2 documents section:

http://www.docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf

Regards!

...JRF...