topic Re: Inode errors ??? in Operating System - HP-UX

Inode errors ???

cl_5 — Mon, 13 Jan 2003 09:19:15 GMT

Hi,

I??ve got installed 3 new C3750 Workstations with HPUX 11.00
Since the systems are up and running I receive the following error message:
2 error 6
msgcnt 59011 vxfs: mesg 016: vx_ilisterr - / file system error reading inode 44056
msgcnt 59012 vxfs: mesg 008: vx_direrr: vx_dirlook_4 - / file system inode 35455 block 696382 error 6

thanks for help

Carsten

Re: Inode errors ???

RAC_1 — Mon, 13 Jan 2003 09:25:02 GMT

seems problem reading mentioned inode.

do full fsck on filesystem

Re: Inode errors ???

T G Manikandan — Mon, 13 Jan 2003 09:26:38 GMT

run fsck on the file system

#fsck -F vxfs -y -o full /dev/vgxx/lvol...

Re: Inode errors ???

Armin Feller — Mon, 13 Jan 2003 09:28:17 GMT

Hi,

please find the disk or lvol where the inode is located on:

# find / -inum 44056

Then umount the filesystem and run an fsck:

# fsck -o full /dev/rdsk/c...
or
# fsck -o full /dev/vgXY/rlvolX

Regards ...
Armin

Re: Inode errors ???

RAC_1 — Mon, 13 Jan 2003 09:30:20 GMT

ls -ali

check your files/dirs

do dd if=your_file/dir of=/dev/null bs=1k

check for errors.

Re: Inode errors ???

Bill Hassell — Mon, 13 Jan 2003 13:04:26 GMT

The key here is the error number (in Unix, it is known as errno). From the file: /usr/include/sys/errno.h:

ENXIO 6 /* No such device or address

Since this is the root filesystem, we can rule out the "no such device" part of the error message, but the "address" is likely the problem. It would appear that the filesystem is trying to access an area beyond the end of the logical volume. Did someone (as root) run the lvreduce command? If so, it will always work but it will also destroy filesystems since LVM commands know nothing about filesystems. LVM simply carves the disk into logical sections and some of these sections may contain a filesystem.

If you've been using lv commands to 'adjust' the size of lvol1, lvol2 or lvol3 (/stand, primary swap and / respectively), you may have some fairly serious problems with the filesystems. If possible, use lvextend to put back the original definitions. Then (download if necessary) use Ignite/UX to backup vg00 and restore interactively so you can adjust all the lvol sizes.