msgcnt x: mesg 003: V-2-03: vx_mapbad - mount_point file system

[Michael Steele_2]

Hello Gang:

I'm posting this as a future reference just because it was so odd and I couldn't find a thread for 'mapbad' on the itrc. Hee's the syslog error:

"...msgcnt x: mesg 003: V-2-03: vx_mapbad - mount_point file system free extent bitmap in au aun marked bad..."

We had a box with this error which showed up in syslog.log and reported root (/) at 100%. It was a false alarm. The actual space problem was 61%. There were no runaway processes, no open files, just a bug in online JFS 4.1. Here's the symmantic / veritas link with the solution:

http://sfdoccentral.symantec.com/sf/4.1/solaris64/pdf/vxfs_admin.pdf

I couldn't help but wonder if other SA's had just rebooted to overcome the problem, when in fact, its basically harmless. The box did not act like a hung or non-responsive box which is what you would expect when root (/) goes to 100%. There were some small issues with the shell like 'history' wouldn't work, but nothing else. And only 'du' caught the correct file system size. 'bdf' didn't. 'df' didn't. Check this out:

du -kx / | sort –rn | more

139752 / <= Right there. / is only 139752 on asap81 or 61%
89536 /etc
48608 /sbin
40192 /etc/vx
29472 /etc/vx/static.d
28760 /etc/vx/static.d/build
####################
Here’s bdf

bdf /

msgcnt 3565 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)

Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 212992 212992 0 100% /
#####################
Here’s ‘df’

df -sk /

msgcnt 3567 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)

/ (/dev/vg00/lvol3 ) : 212992 total allocated Kb
0 free allocated Kb
212992 used allocated Kb
100 % allocation used

So that's it and good luck.

[Michael Steele_2]

.