kernel vx_ilisterr error message

[Conrado Camacho]

Hello everyone, Please help
I have two more questions. My syslog is reporting an error message: "vmunix: vxfs: mesg 016: vx_ilisterr - / file system error reading inode 64" (and 65). Does this indicate that another disk needs to be replaced?

I have and old HP server 9000 D370 with HP-UX 11.0.

On the other hand, I am also receiving in my syslog a message "/sbin/lvlnboot -v vg00" and I am not executing the command, is this normal?

Thanks in advance for your valuable help

Regards
Camacho

[Steven E. Protter · Accepted solution]

Shalom Camacho,

Yes, the best course of action is to replace the disk. The problem is probably due to a bad disk sector.

The command you refer to is probably being issued by a cron script. It displays boot characteristics.

crontab -l, check the scripts.

SEP

[Sandman!]

Not neccesssarily but you should run dd(1) against it to see if it fails:

# dd if=/dev/vg00/rlvol of=/dev/null count=100 bs=1024k

Or it could be a filesystem metadata integrity issue as ilisterr is related to the inode list. Usual thing would be to unmount the filesystem and fsck it. But as this is the root filesystem you most likely have to reboot.

[Joelmel Roche]

Hi,
When the kernel allocates an inode from the free inode bitmap, it checks the
mode and link count of the inode. If either is non-zero, the free inode bitmap
or the inode list is corrupted. The VX_FULLFSCK flag is set in the super-block
so that fsck will do a full structural check the next time it is run.

ACTION:

Unmount the file system and use fsck to run a full structural check.

[Conrado Camacho]

Thank you very much for your help.

As expected, your help has been very valuable.

I will apply suggestions

Regards,

Camacho