Due to an incompatibility in the VxFS fsck
utility between the 5.0 and 4.0 and 4.1 releases, fsck
may abort during intent log replay if run on older file systems. This only affects file systems that were previously running under VxFS 4.0 or 4.1 that are CVM-shared volumes or multi-volume file systems, and that were not cleanly unmounted prior to use in VxFS 5.0.
If you encounter this situation, perform a full fsck
to bring the file system to a consistent, clean state that is ready to be mounted.
See the fsck_vxfs
(1M) manual page.