Inode error

[Kavita Poonia]

Hello all,

We are getting below error on one of our HP-UX server after installing RMP patch. We have also extended /var at that time. After that we started getting this error.

Nov 30 03:50:27 mccfwp18 vmunix: msgcnt 2 vxfs: mesg 016: vx_ilisterr - /var file system error reading inode 35104

Thanks * regards,
Kavita

[cnb · Accepted solution]

Hi,

Maybe this might help to isolate:
http://docs.hp.com/en/B3929-90011/apas03.html

HTH,

[Kavita Poonia]

Hello CNB,

Thanks for the document. It was really helpful. That means we have to replace the disk or either run fsck to correct this error. But why this error got generated, any idea ?

Thanks * regards,
Kavita

[cnb]

Hi Kavita,

I suspect the disk being extended might have had something to do with it. Could be a bad block. Not really sure, but you could run STM & logtools against the drive to see the hardware health history of the drive.

Check with:
# echo "sel dev all;info;wait;il"|/usr/sbin/cstm
-and-
# cstm
cstm> runutil logtool
Logtool Utility> rs
Logtool Utility> fs
Logtool Utility> fl


HTH

Regards,

[Bill Hassell]

> vxfs: mesg 016: vx_ilisterr - /var file system error reading inode 35104

This is an I/O error which means the disk could not be read (bad spot). Look in syslog and you'll likely see a lot of I/O error messages. You can also use dd to verify that the disk has a bad spot:

dd if=/dev/vg00/whatever of=/dev/null bs=1024k

The bad spot will cause dd to stop with I/O error 5. You'll need to replace the disk and recover all the data on it.

Since you said you extended /var, did you use Online JFS, ie, the fsadm command to increase the filesystem?

[Kavita Poonia]

Thanks CNB for your reply......



Hello Bill,

I have tested the disks with dd comand and it seems fine. Yes, I have used fsadm for extending /var. I have also logged a CASE with HP and they have suggested to install 3 network patches on the server.


Thanks * regards,
Kavita