Data corruption is an extremely rare event. No SAN should corrupt data just because of a "controller glitch" - efficient designs generally safeguards against this.
I'd like to recommend that you check /var/log/vmkwarning for any error messages that might give you additional clues. On the odd chance that the LUN is being detected as a snapshot, that's relatively easy to address (resignaturing or simply correcting the LUN presentation from the controller side.)
If you truly believe that the VMFS file system has been damaged, your best recourse is to log a support call with VMware. There are no public tools to repair VMFS, but PSS have some tools and methods available to them that - I have heard - can work miracles.
Also, as with corruption on any platform, proper diagnosis before action is definitely recommended. Until you know exactly what happened, avoid trying anything that will cause changes being writted to the LUN. Every time you write anything, chances of recovery diminish. If you do do something, document what you have done exactly so that you can pass that information on to PSS.
.png "jhanekom"){kind=avatar}
