Volumes can become corrupt no matter what file system you are talking about (er, there might a magical file system out there that cannot become corrupted but I’ve never heard of it and would like to sell a certain bridge to you if you have). Xsan is no different and so you need to be ready to use the command line to combat said corruption. fsck is the traditional *nix tool to fix issues with volume corruption. cvfsck is the weird cousin that’s used for Xsan. If you see any iNode errors in your logs, corruption errors, high latency or just too many weird issues to shake a stick at then use cvfsck to check for errors. It can be run in a non-destructive mode (it is by default actually). If errors are found then, if possible, backup the SAN immediate as cvfsck could cause the volume to get shredded (or more commonly for specified files on the volume to become unuseable). Then you can use cvfsck to repair the volume.