LSI driver bug is breaking VSANs, endangering data

VMware says its VSAN virtual storage array is selling well, earning hardware-makers' attention and making plain the wisdom of the software-defined data centre. It may well be, but VSAN is also having some teething problems. Back in July, VMware was forced to change its recommended VSAN system configurationsbecause VSANs were …

[Velv]

It might not be VMWares fault, but it is VMWares problem if it affects a substantial proportion of the installed estate.

One can only hope that VMWare is working very closely with LSI to help resolve the issue.

[Sandtitz]

40 days? Pah!

Even Windows 95 managed 49.7 days before crashing!

[DeepStorage]

It sure is VMware's fault. They certified the driver

The strength of EVO:RAIL is supposed to be that there's only one hardware config and that VMware's tested the crap out of that config.

Note that the only SAS HBAs, as opposed to RAID controllers, on the VSAN HCL are LSI based even if like the HP H200 they're OEM versions.

If you tell customers not to buy RAID controllers, only have one non-RAID controller driver supported and then have problems it's as much your fault as the vendor that wrote the controller. VMware's testing needs a major upgrade.