vxfs error - mesg 004 vx_mapbad

[Mike Berry_2]

Hi all
Just got a message from a 10.20 box:
"vmunix: vxfs: mesg 004: vx_mapbad - /u02 file system free inode bitmap in au 1 marked bad"

"bdf -i" shows -

iused ifree %iuse
33096 96196 26%

Machine is patched to December 2001

Any ideas???


Mike

[Steve Steel]

Hi

Try

http://bizforums.itrc.hp.com/cm/QuestionAnswer/1,,0x5ee7911284f5d5118ff40090279cd0f9,00.html


Steve Steel

[Mike Berry_2]

Thanks Steve

I had actually seen this message on the forum, but was concerned that the message number was different. I don't know if this is a critical difference or not. I am prepared for an fsck later today, but if this problem denotes a faulty disk, I would prefer to just slap a new one in instead.


Thanks again.


Mike

[S.K. Chan]

As far as the error message is concerned, there is "possible" an IO error. What happens is the kernel stop allocation resource to the to the map due to bad vxfs map while writing a bitmap to it. You need to check the system log file for any IO errors. Also use "cstm", if possible run exerciser on the disk. If you don;t see ant hardware error after you run exerciser, I would then perform an fsck (full-structural check eith the filesystem umount). The command to do that would be ..
# fsck -F vxfs -y -o full /dev/vgXX/lvolY

[Sanjay_6 · Accepted solution]

Hi Mike,

Looks like what you need is a patch. Check out this patch. The latest patch in the category is,

http://support2.itrc.hp.com/service/patch/patchDetail.do?patchid=PHKL_20728&context=hpux:800:10:20

The patch that solved the problem faced by you was PHKL_16919.

Also check out the other associated patches.

Hope this helps.

Regds

[Mike Berry_2]

Thanks for your help everyone.

I ran a full fsck on this disk and everything looks OK for the moment. This box is running a bunch of old disks, so I'll put it down to that.

Cheers


Mike