Error Message

V-2-17: vx_dirlook. /dev/vx/dsk/DG_name/VOL_name  file system inode NNNNNN marked bad incore

V-2-16: 

Typically unknown - IO errors on LUN. Also forced umounts of the volume especially in cluster environment.

Error is  /dev/vx/dsk/DG_name/VOL_name  file system inode NNNNNN marked bad incore:

Volume is /dev/vx/dsk/DG_name/VOL_name

Errored VxFS syscall is vx_dirlook  - a directory lookup - some directory inconsistency

# ff -t vxfs -i NNNNNN /dev/vx/rdsk/DG_name/VOL_name
This should indicate the FILE_name

Check also that the V-2-16 or V-2-17 object matches the file type IFDIR (directory) or IFREG (regular file) or IFSOC ( socket ).

# echo "999fset.NNNNNNi" | fsdb -t vxfs /dev/vx/rdsk/DG_name/VOL_name

# ncheck -t vxfs -o block=   /dev/vx/rdsk/DG_name/VOL_name  | grep FILE_name
This should return the file system blocks in the volume containing this file - note file system blocks usually are 1024 bytes, device sectors are usually 512 bytes.
You can check file system block size with the following command
# echo "8192B.p S" | fsdb -t vxfs /dev/vx/rdsk/DG_name/VOL_name   | grep bsize
 

# vxprint -htg DG_name VOL_name
Look for corresponding subdisks sd records containing the offsets
 

# vxprint -dg DG_name
Identify the corresponding DMP_names
 

# vxdisk list DMP_name
Look at the bottom of this output for the corresponding OS devices.

Check in iostat -En, /var/adm/messages for any errors on these devices and / or check in /etc/vx/dmpevents.log for the DMP_name disabled.
 

Applies To

The following commands are specific to Linux platforms. Change options for other supported platforms.