Emulex Drivers Causing issues with ESXi RamDisk and Scratch Config

I’m a bit late to the blogosphere with with one, but we’ve had a couple of customers hit the issue described below, and it seems to be mostly across HPE and Dell hosts running ESXi 6.x. I’ll get to the good stuff first. If you’re hitting an issue on ESXi 6.x where the RamDisk is filling up and¬†ScratchConfig.CurrentScratchLocation is reverting to /scratch, even with a location configured, it’s likely due to a known issue with an Emulex Driver.