[Veritas-vx] I/O errors on an vxfs filesystem
greg.robinson at dsto.defence.gov.au
Thu Apr 1 19:13:36 CST 2004
Similar to Balki, we appear to have a dead disk in our storage array, but my question is, how do I determine which disk is dead?
we found vxfs had disabled /export/home on one of our servers this morning (Solaris 8, vxvm 3.5 MP1).
df showed cannot stat: I/O error.
vxprint -hrt showed everything was fine, nothing disabled.
After a umount -f and a fsck -o full, I could remount the volume. It is still showing a bad inode:
hostname: vxfs: vx_ilisterr: vx_iread_3 - /export/home filesystem error reading inode 151228
hostname: vxfs: vx_ialloc - /export/home filesystem inode 151228 not free
hostname: vxfs: vx_ilisterr: vx_ialloc - /export/home filesystem error reading inode 151228
This disk is attached to a Sun A3510, and it a single LUN, then is is "sliced" at the host using vxvm. How can I determine which disk I need to replace in the raid set?
There are no errors on the 3510, and there is no read flashing light or alarm (yes I checked the obvious).
Thankx for any help,
More information about the Veritas-vx