When I started out with ESX 3.0.x the first thing I wanted to do was disable the VMFS-2 driver. There’s no need for it when you’re not accessing VMFS-2 volumes and removing it can lead to performance gains or at least a faster rescan of your storage. Removing it, according to to this section of the VMware website, was supposed to be really easy:
vmkload_mod -u vmfs2
Unfortunately, this just unloads the module and every time the server gets rebooted the module is loaded again. Same goes for the esxcfg-module command, it unloaded it but after a reboot the module was loaded again. You could add the command to /etc/rc.local of course. This would unload the module every time the server booted. I’m not a big fan of manually changing files like this, and luckily as of the next generation of ESX(vSphere) this doesn’t seem to be necessary anymore:
esxcfg-module -d -d|--disable - Disable a given module, indicating it should not be loaded on boot.
The funny thing is when I run the “esxcfg-module -l” command it still lists the module as loaded. If I run the “esxcfg-module -q”, which only queries the enabled modules, it’s not listed. After a closer investigation I noticed that the following line changed in “/etc/vmware/esx.conf”:
/vmkernel/module/vmfs2/enabled = "false"
I did a cross-check, it’s most definitely not loaded. Cool, remember this one “esxcfg-module -d”. It will come in handy some day.