It has to do with: mptscsi adds DID_BUS_BUSY host status when scsi status of BUSY is returned Short description: When the SCSI I/O command is returned to the Linux SCSI midlayer with a host status of DID_BUS_BUSY, the command will be retried five times and then if the target continues to return a status of
There is a bug somewhere that causes this problem on a host. The host thinks the resource pool is not there, VC says, go ahead add it, but it already exists. You will go into a loop. Do NOT turn off DRS, this will remove all your resource pools, but put it on partial automated.
Today one of the SAN’s thought it was vacation. A nice error showing there was something wrong ‘vmware Failing I/O due to too many reservation conflicts’ Reading through http://kb.vmware.com/kb/1005009… Checked the volume on the console and could not even enter the directory. Management of the SAN was also unreachable. Rebooted the SAN.
Yesterday i added a local user to vSphere 4 host with the vSphere client. I forgot the ‘shell access’ box. After that i enabled the box for shell access, when logging in, the home directory did not exist. Solution for this: cd /home mkdir username chown username dirname chmod 700 dirname
I will be posting vmware things i run into during my day job. This is the first post \o/ I did my vcp-410 exam on 18-dec-2009 with a score of 488/500 🙂