First off let me say that I did a lot of searching on this forum and others trying to find an answer to this issue I have please try not to flame me to bad.
Second I would like some what of a solid answer if this issue if fixable via some switch I am missing.
Now Onto my issue.
I am control of Two ESX machines where I work. They are Both IBM X 3550 M3 systems. They have both been upgraded to ESXi 5.1 from 4.1. One of the machines is having no issues what so ever but the 2nd machine is having the Datastore uploading issue.
The First ESX machine is a 2 socket 8 core machine whereas the 2nd machine is a 2 socket 4 core machine. They both have 64 gb of memory.
The first machine has two 600 gb 10k drives Mirrored together.
The second machine has 4 600 gb 10 k drives Striped Mirrored.
I am for right now using FileZilla to upload my ISO's to the machine which is grand scheme is okay but not that best solution as the built in DataStore browser on the 1st machine is working with no issues whereas the 2nd machine is not.
I can upload, on the 2nd machine, about about 25% of the ISO and then it kicks an I/O error to me. The 2nd machine has 4 NICs all of which are gb interfaces all of which are enabled on a layer 2 3750 switch.. They are on Auto Negotiate which is what every one is saying it should be on. I have yes forced them to 1000mb FD and that has not fixed the issue.
I know others are having this issue. Any help would be awesome.
Any error message triggered in /var/log would be helpful to troubleshoot. If possible check and share that information:
message,hostd.log,vpxa.log
-A
Take a look at the vSphere client logs from the system where you are trying to upload the files.
AFAIK when you try to upload files from data store browser one of the ESXi hosts is selected by vCenter irrespective of the ESXi host that you select during file upload.
-f10
http://highoncloud.blogspot.in
About VMware Virtualization on NetApp
ok just log to the esxi host thru vsphere client and upload the file to data store and take a look in to vmkernal warning logs, you would may be receive VMFS heap size warning if the warning is there then try to increase heap size warning to maximium size in settings. why i'm saying this because VMFS heap memory is handling VMFS data store related process, so try to check by this way.
dhanarajramesh Thank you for the suggestion. I did check the VMFS Heap size it was set to 80. I moved it to the max of 256 rebooted the host and had one of my Co-workers attempt to upload an ISO . I am still having the same issue.
Bump to recognize
