UnixPedia : HPUX / LINUX / SOLARIS: HPUX : /stand corruption.

Thursday, March 20, 2014

HPUX : /stand corruption.

Ignite is failing on the server , with error related to stand.

root@thames:/.root]#
#-> ll /stand/current/mod/
/stand/current/mod/gvsd.prep not found
/stand/current/mod/iether.prep not found
 /stand/current/mod/iexgbe not found
 /stand/current/mod/iexgbe.prep not found
 /stand/current/mod/igelan not found
 /stand/current/mod/igelan.prep not found
 /stand/current/mod/iocxgbe not found
 /stand/current/mod/iocxgbe.prep not found
 /stand/current/mod/iqxgbe not found
 total 136352
-r--r--r--   2 bin        bin        4865080 Jan 31  2012 atdd_core
-r--r--r--   2 bin        bin         687920 Feb  9  2009 btlan
-r-xr-xr-x   2 bin        bin           4595 Feb  9  2009 btlan.prep

syslog :

Mar 12 15:30:27 thames vmunix: vxfs: WARNING: msgcnt 3709 mesg 016: V-2-16: vx_ilisterr: vx_iread_2 - /stand file system error reading inode 128
Mar 12 15:30:27 thames vmunix: vxfs: WARNING: msgcnt 3710 mesg 008: V-2-8: vx_direrr: vx_dirlook_4 - /stand file system dir inode 125 dev/block 0/17713 dirent inode 128 error 6
Mar 12 15:30:27 thames vmunix: vxfs: WARNING: msgcnt 3711 mesg 016: V-2-16: vx_ilisterr: vx_iread_2 - /stand file system error reading inode 129
Mar 12 15:30:27 thames vmunix: vxfs: WARNING: msgcnt 3712 mesg 008: V-2-8: vx_direrr: vx_dirlook_4 - /stand file system dir inode 125 dev/block 0/17713 dirent inode 129 error 6


And there are a larger number of these all pointing at /stand which is the cause of the ignite failure.  The error 6 is no such device or address meaning it cannot find what it expects at that inode. This is an indication of file system corruption.  Normally it would be a bad disk but I do not see any errors on the root disks and none of the other file systems in vg00 are complaining. Running a dd to /dev/null on both disks would also be a good idea to verify there is not a disk problem.
# dd if=/dev/rdisk/disk2 of=/dev/null bs=1024k
# dd if=/dev/rdisk/disk3 of=/dev/null bs=1024k
If that comes back with no errors then I would suggest restoring /stand from backup if we have a current backup.



recommendation :

Unmounted /stand and run fsck against it.

# umount /stand
# fsck -o full /dev/vg00/rlvol1
# mount /stand

No comments:

Post a Comment