ESX 3.5 Update 2 - vmkernel messages FileIO failed with 0x0xbad0006(Limit exceeded)

[bigdee]

Hi gents

I updated four of our ESX hosts to 3.5 Update 2. The hosts all had ESX 3.5 Update 1 installed with the latest patches. After a reboot of the host the following entries are added to the vmkernel logfile for all physical CPUs:

Jul 30 13:29:57 svstr18003 vmkernel: 0:00:02:23.455 cpu2:1035)BC: 814: FileIO failed with 0x0xbad0006(Limit exceeded)

Jul 30 13:29:57 svstr18003 vmkernel: 0:00:02:24.414 cpu2:1036)BC: 814: FileIO failed with 0x0xbad0006(Limit exceeded)

Jul 30 13:29:57 svstr18003 vmkernel: 0:00:02:24.504 cpu2:1035)BC: 814: FileIO failed with 0x0xbad0006(Limit exceeded)

Jul 30 13:29:57 svstr18003 vmkernel: 0:00:02:24.626 cpu3:1037)BC: 814: FileIO failed with 0x0xbad0006(Limit exceeded)

...

Beside of that I have noticed no other issues. The hosts seem to run fine!

Has anyone experienced something similar or knows what this messages mean?

Thanks

CU

[Dollar]

Thanks, worked for me.

I created a functional "logfiles" containing exclusions for "FileIO failed with 0x0xbad0006", distributed that file (overwriting the existing file) to all of my hosts, and then processed the following commands on each host:

killall -HUP vmklogger

/usr/sbin/vmklogger &

/etc/init.d/syslog restart

Worked like a champ and took a few minutes to knock out a 160 hosts.

Secondary question, are folks also seeing the "Debug SCSI Underrun" on their servers associated with this same issue?

[sharvey2]

Same thing greyhound reported. 3.5U2. HP blade environment. All blades logging the message and we understand that it is not a problem. According to Vmware Support a debug flag was left on and it will be corrected in next update. Problem we have is one blade that is logging the message dozens of times about every minute. All other blades get the message but at a MUCH lower frequency -a couple every few days-

Because of this we suspect some kind of hardware problem with the noisy blade. We can stop the messages by stopping pegasus. service pegasus stop

We have re-installed ESX on the noisy blade to no avail.

Is anyone else getting this message at a high frequency?

[Goliath222]

Hi,

found this solution on a website :

Solutions after ESX 3.5 U2

1. Raise VMFS3 Limit on Server/Configuration/Advanced/VMFS3/VMFS3MaxHeapSizeMB from 16 to 64 or even 128 MB

For me it works fine, no more messages in vmkernel. Second solution would be to exclude the messages from vmkernel, which can be done :

1) Add following line to /etc/vmware/logfilters

3 xbad0006

Restart the vmklogger

2) killall -HUP vmklogger

Hope this helps.

Regards.

[IB_IT]

Same issue here with Update2 and Sun x4600M2's with Qlogic. Has anyone on this thread been patched up to build #130756 and still experiencing this?

[IB_IT]

FYI all,

VMware just updated the kb...it now shows that update 3 is the fix for this.

1004499

[milling]

I'm not sure if this is still a problem for anyone but we also had this error message in our cluster and we resolved it by increasing the Service Console memory to 800MB from the default 272MB. The error message has now dissapeared from the logs. We also had hosts becoming unresponsive "not responding" in the cluster and the memory increase has resolved that issue as well.

Hope it helps.

thanks,

[dan81]

<![endif]><![if gte mso 9]>

<!--

/* Font Definitions */

@font-face

{font-family:"Cambria Math";

panose-1:2 4 5 3 5 4 6 3 2 4;

mso-font-charset:0;

mso-generic-font-family:roman;

mso-font-pitch:variable;

mso-font-signature:-1610611985 1107304683 0 0 159 0;}

@font-face

{font-family:Calibri;

panose-1:2 15 5 2 2 2 4 3 2 4;

mso-font-charset:0;

mso-generic-font-family:swiss;

mso-font-pitch:variable;

mso-font-signature:-1610611985 1073750139 0 0 159 0;}

@font-face

{font-family:Consolas;

panose-1:2 11 6 9 2 2 4 3 2 4;

mso-font-charset:0;

mso-generic-font-family:modern;

mso-font-pitch:fixed;

mso-font-signature:-1610611985 1073750091 0 0 159 0;}

/* Style Definitions */

p.MsoNormal, li.MsoNormal, div.MsoNormal

{mso-style-unhide:no;

mso-style-qformat:yes;

mso-style-parent:"";

margin:0in;

margin-bottom:.0001pt;

mso-pagination:widow-orphan;

font-size:11.0pt;

font-family:"Calibri","sans-serif";

mso-ascii-font-family:Calibri;

mso-ascii-theme-font:minor-latin;

mso-fareast-font-family:Calibri;

mso-fareast-theme-font:minor-latin;

mso-hansi-font-family:Calibri;

mso-hansi-theme-font:minor-latin;

mso-bidi-font-family:"Times New Roman";

mso-bidi-theme-font:minor-bidi;}

p.MsoPlainText, li.MsoPlainText, div.MsoPlainText

{mso-style-noshow:yes;

mso-style-priority:99;

mso-style-link:"Plain Text Char";

margin:0in;

margin-bottom:.0001pt;

mso-pagination:widow-orphan;

font-size:10.5pt;

font-family:Consolas;

mso-fareast-font-family:Calibri;

mso-fareast-theme-font:minor-latin;

mso-bidi-font-family:"Times New Roman";

mso-bidi-theme-font:minor-bidi;}

span.PlainTextChar

{mso-style-name:"Plain Text Char";

mso-style-noshow:yes;

mso-style-priority:99;

mso-style-unhide:no;

mso-style-locked:yes;

mso-style-link:"Plain Text";

mso-ansi-font-size:10.5pt;

mso-bidi-font-size:10.5pt;

font-family:Consolas;

mso-ascii-font-family:Consolas;

mso-hansi-font-family:Consolas;}

.MsoChpDefault

{mso-style-type:export-only;

mso-default-props:yes;

mso-ascii-font-family:Calibri;

mso-ascii-theme-font:minor-latin;

mso-fareast-font-family:Calibri;

mso-fareast-theme-font:minor-latin;

mso-hansi-font-family:Calibri;

mso-hansi-theme-font:minor-latin;

mso-bidi-font-family:"Times New Roman";

mso-bidi-theme-font:minor-bidi;}

@page Section1

div.Section1

-->

Hi,

I have the same problem but i don`t do anything before.

after the esx 3 restart automatically than i check /var/log/vmkernel and i find this error

"Jun 2 14:26:01 vms2 vmkernel:

7:23:34:40.023 cpu1:1034)BC: 814: FileIO failed with 0x0xbad0006(Limit

exceeded) "

please help

thanks

dan81