Is it possible that the new driver shifted you read/write % on the raid controller, or maybe changed the write cache settings?
Boot up one of the hosts with HP's Offline Array Control Utility and check the RAID controller settings. You can also change your % here if your workload is more read. Back when we used to deploy a lot of HP servers for Disk-to-Disk-to-Tape systems I would change the RAID controller settings to 80% write 20% read as the backup server was doing 80% writing anyhow.
Hope this has helped
Good point, but I've already checked the cache settings, and they are still 50/50 for read/write in our case, because read latency is the problem here, not write latency. We've also checked the BBWC module, and it's working fine.
most probably, you have already solved the issue... I made some investigation and was in contact with HP. This is issue with hpsa-18.104.22.168 driver. It crashes from time to time when used with P410i. In logs, you can find "WARNING: LinScsi: SCSILinuxAbortCommands:1843: Failed, Driver hpsa, for vmhba0". HP knows about it and working on new driver. As workaround, you can use hpsa-22.214.171.124 (at least this works well for us).
many, many thanks maaca! No, I did not get an answer from our HP partner. Because of you post I can finally do something against all that monitoring alerts. I'll install hpsa-126.96.36.199 in our testing lab and roll it out as soon as I'm sure it works!
Thanks again and best regards!
this issue still exist also in 106 (scsi-hpsa-188.8.131.52-1OEM.5184.108.40.2061820.x86_64.vib).
HP works on ver.110, but it seems to be unstable and HP-customized 5.5U3a will be released with 106 again.
The only workaround we found: to unconfigure spare drive from RAID5 volumes.
You are right. Now I see it also. Somehow, it didn't appear in our lab, but I can see it in production.
So the only stable versions are .60 and .84, right?
>>Somehow, it didn't appear in our lab
is the spare disk configured for your RAID LUNs in your lap environment ?
If not, could you please try to reproduce it?
>> So the only stable versions are .60 and .84, right?
I didn't downgrade scsi-hpsa driver, because the statement from HP: ..If the events: "Lost access to volume + Successfully restored access to volume" appear periodicaly (10-30 minutes cycle), they can be ignored.
HP call is opened. HP promized me to release the driver next months.
yes, this seems to be correct. We don't have configured spare disks in our lab.
we had the same problem with 106 after update HP driver und VMware 5.5 to U3. I made a manual downgrade from 106 to 60 this worked for me, but write performance is still bad (cache settings is 25% read and 75% write).
We have still hotspare hd defined on raid 5 , maybe i try to unconfigre this and look if something gets better. The new Version 110 is still not available...
ESXi 5.5 U3a ISO (HP customized: VMware-ESXi-5.5.0-Update3-3116895-HP-5220.127.116.11-Nov2015.iso) is available for download:
it looks the HPSA module was released in the version 114:
scsi-hpsa 18.104.22.168-1OEM.522.214.171.1241820 Hewlett-Packard VMwareCertified
Could you please post results, if anyone of you going to test this release/driver?
we are running on .114 for few days on few hosts and it seems to be stable.
Apparently Problems still exist with the updated 114 HPSA Driver opened a new thread
Datastore / Disk latency problems with HP ProLiant G7 - HP Smart Array P410i controller " WARNING: LinScsi: SCSILinuxAbortCommands:1843: " and "Lost access to volume" (Still an issue with hpsa 126.96.36.199-1OEM )