Straight up when I putty into the ESX 3.0 server, I can scan and view all of my LUN's. The problem I am having is when i view the vmdk and flat.vmdk files directly on the Server they are not the same vmdk files that you view on the infrastructure client/guest OS(Luns look the same). I would think these vmdk files should match up.... its as if i am looking at 2 different servers.
I have the esx server connected to a SAN via fiber.
Below is the text from the ssh session to the vmware server. I also attached a file that views the same LUN's but views different vmxd files when viewed from the infrastructure client.
Bfs1dr_1-flat.vmdk Bfs1dr_1.vmdk Bfs1dr_4-flat.vmdk Bfs1dr_4.vmdk
Straight up when I putty into the ESX 3.0 server, I can scan and view all of my LUN's
Has anything been changed with these VMDK files? It's peculiar you shut them down, which means you probably increased the space. They are now 2 TB (1TB each). 2TB is the maximum volume size. So now you need a swap file for the VM, and since you are already over your limit, you may be out of luck. You may need to call VM ware for this one. I believe the problem is there isn't any more room to allocate space for the swap files on a VMFS volume.
nothing has changed to my vmdk files.
It looks to be an incorrect mapping issue somewhere. Why is the vmware server saying we have both Bfs1dr4.vmdk, Bfs1dr1.vmdk(from console/ssh) and the through the client it is saying I have bfs1dr5.vmdk and bfs1dr7.vmdk?
this is along the lines of what i am talking about, although the suggestions to fix the problem did not work.