System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

vx_ilisterr: vx_iread - / file system error reading inode ERROR

JustPranav
Occasional Contributor

vx_ilisterr: vx_iread - / file system error reading inode ERROR

Hi Team,

 

HP-UX m7 B.11.23 U 9000/800 4059557779 unlimited-user license.

 

I am getting the following errors in my syslog:-

 

Can any one help, what will be the work around.

 

 

Aug 28 19:00:22 m7 vmunix: msgcnt 290453 vxfs: mesg 016: vx_ilisterr: vx_iread - / file system error reading inode 7045
Aug 28 19:00:22 m7 vmunix: msgcnt 290454 vxfs: mesg 017: vx_iread - / file system inode 7045 marked bad incore
Aug 28 19:01:01 m7 vmunix: msgcnt 290455 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9422
Aug 28 19:01:19 m7 vmunix: msgcnt 290456 vxfs: mesg 016: vx_ilisterr: vx_iread - / file system error reading inode 7063
Aug 28 19:01:19 m7 vmunix: msgcnt 290457 vxfs: mesg 017: vx_iread - / file system inode 7063 marked bad incore
Aug 28 19:01:47 m7 vmunix: msgcnt 290458 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9370
Aug 28 19:01:47 m7 vmunix: msgcnt 290459 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9420
Aug 28 19:01:47 m7 vmunix: msgcnt 290460 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9372
Aug 28 19:01:50 m7 vmunix: msgcnt 290461 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9358
Aug 28 19:01:50 m7 vmunix: msgcnt 290462 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9356
Aug 28 19:02:16 m7 vmunix: msgcnt 290463 vxfs: mesg 016: vx_ilisterr: vx_iread - / file system error reading inode 7063
Aug 28 19:02:16 m7 vmunix: msgcnt 290464 vxfs: mesg 017: vx_iread - / file system inode 7063 marked bad incore
Aug 28 19:02:44 m7 vmunix: msgcnt 290465 vxfs: mesg 016: vx_ilisterr: vx_iread - / file system error reading inode 7045
Aug 28 19:02:46 m7 vmunix: msgcnt 290466 vxfs: mesg 017: vx_iread - / file system inode 7045 marked bad incore
Aug 28 19:03:02 m7 vmunix: msgcnt 290467 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9422
Aug 28 19:03:12 m7 vmunix: msgcnt 290468 vxfs: mesg 016: vx_ilisterr: vx_iread - / file system error reading inode 7063
Aug 28 19:03:12 m7 vmunix: msgcnt 290469 vxfs: mesg 017: vx_iread - / file system inode 7063 marked bad incore
Aug 28 19:04:09 m7 vmunix: msgcnt 290470 vxfs: mesg 016: vx_ilisterr: vx_iread - / file system error reading inode 7063
Aug 28 19:04:09 m7 vmunix: msgcnt 290471 vxfs: mesg 017: vx_iread - / file system inode 7063 marked bad incore
Aug 28 19:04:37 m7 vmunix: msgcnt 290472 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9370
Aug 28 19:04:37 m7 vmunix: msgcnt 290473 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9420
Aug 28 19:04:37 m7 vmunix: msgcnt 290474 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9372
Aug 28 19:04:37 m7 vmunix: msgcnt 290475 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9358
Aug 28 19:04:37 m7 vmunix: msgcnt 290476 vxfs: mesg 016: vx_ilisterr: vx_iread_2 - / file system error reading inode 9356

4 REPLIES
Dennis Handly
Acclaimed Contributor

Re: vx_ilisterr: vx_iread - / file system error reading inode ERROR

What is providing the storage for the filesystem, a SAN?

If a local disk, do you have any media errors?

Bill Hassell
Honored Contributor

Re: vx_ilisterr: vx_iread - / file system error reading inode ERROR

Possibly filesystem corruption but more likely the disk is going bad.

You can run a quick read test of the vg00 disk using the dd command.



Bill Hassell, sysadmin
JustPranav
Occasional Contributor

Re: vx_ilisterr: vx_iread - / file system error reading inode ERROR

this the prod box..i dont want to run dd on root filesystem..it may hamper!!!
Any Other suggestion ..?

Bill Hassell
Honored Contributor

Re: vx_ilisterr: vx_iread - / file system error reading inode ERROR

You would run the dd command to simply read the disk.

You have very serious filesystem corruption, possibly caused by a disk crash or a bad spot.

The dd command would just verifiy the problem.

The fix is to backup everything on this particular disk as soon as possible.

Bad spots on disks never get better -- it will get worse and then the disk usually fails completely.

Look for the words "I/O error" in syslog.

Your production system is about to fail...



Bill Hassell, sysadmin