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.
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
