filesystem meta data read error

[Shaamil]

Hi GURUS
I get this message when I check in the syslog file.:
vxfs: mesg 016: vx_ilisterr - /opt/pbin file system error reading inode 1522
vxfs: mesg 055: vx_metaioerr - /dev/pbin/pbin file system meta data read error
vxfs: mesg 016: vx_ilisterr - /opt/pbin file system error reading inode 1526

Can anyone help me.
When I do a filesystem check, it fails.
Also when I do a listing of the filesystem, it says file not found for a couple of files.

Thanks in advance
Shaamil Thorne

[John Carr_2]

Hi

try taking the server to single user mode

making sure /opt is umounted then

fsck -F vxfs /opt

cheers
John

[S.K. Chan]

It sure looks like you got a possible disk problem here. First find out which LV /opt/pbin is in and try to un a full fsck on that LV.
Assuming it's in vg00 (lvol6)
# fsck -F vxfs -y -o full /dev/vg00/lvol6
If you are still unable to access the files after fsck, check your lvol, look for any "stale" extents.
# lvdisplay -v /dev/vg00/lvol6 | more
If you see "stale" extents which I think you would the next thing is to confirm if the disk is having problem or not.From the "lvdisplay" command above you will know which disk lvol6 is in. Lets says it's in /dev/dsk/c2t2d0.

Check for io errors ..
# /etc/dmesg
==> any io errors here ?

Run cstm to confirm if disk is faulty or not ..

# cstm
cstm>map
cstm>sel dev
cstm>info
cstm>infolog

If the disk is found to be faulty you'll have to replace it and perform necessary recovery.

[Mark van Hassel]

Hi,

Is your system connected to a SAN ? I've seen these messages when a LUN was assigned to two systems and both systems had file systems created on that LUN.

So if it is connected to a SAN, check if the LUN is also assigned to another system, on which you would probably get the same messages.

HtH,

Mark