"Not Activating since it does not pass activation filter"

Hi All,

I need help with the issues I am encountering on the field.

I have migrated data from DMX3 volumes assigned to a Linux Cluster with two nodes to VMAX running on 5875.135 using Open Replicator Hot Pull. I have used the "FrontEndZeroDetect" option which was supposed to enhance the performance and also mitigate the zero space reclamation as a post-migration activity. Unfortunately, there is a bug in the Enginuity code which caused the DA request buffer to be marked incorrectly as in use.. and consequently crashed two other servers (which were not part of the ongoing migration). EMC Support was called in and a severity 2 case opened to find the root cause. Cleanup was performed and the Enginuity Pack upgrade is scheduled to fix the bug tonight. Meanwhile, the migration was successfully completed and the system admin was able to confirm that everything was running fine then. After four days now, he comes back to me with the following note:

This is the error I’m seeing when trying to activate the Volume Groups, perhaps EMC has seen this issue…

[root@cvoinfs1 ~]# service clvmd start

Starting clvmd:

Activating VG(s):   Not activating cvoinfs1/lvpublic since it does not pass activation filter.

  Not activating cvoinfs1/lvarchive since it does not pass activation filter.

  Not activating cvoinfs1/lvinfinys_root since it does not pass activation filter.

  0 logical volume(s) in volume group "cvoinfs1" now active

  5 logical volume(s) in volume group "VolGroup00" now active

  Not activating cvoinfs2/lvhome since it does not pass activation filter.

  Not activating cvoinfs2/lvapps since it does not pass activation filter.

  Not activating cvoinfs2/lvlanding since it does not pass activation filter.

  Not activating cvoinfs2/lvinfinys_data since it does not pass activation filter.

  0 logical volume(s) in volume group "cvoinfs2" now active

                                                           [FAILED]

I do not understand where the problem could be. I verified the devices (all in RW state, bound to the pool, pool has sufficient free capacity). I do not know what caused him to suddenly have this issue.

Can someone help me if anyone out there had similar issues and found a solution to it.

Thanks,