Veritas InfoScale™ 7.4.2 Release Notes - Solaris
- Introduction
- Requirements
- Changes introduced in 7.4.2
- Fixed issues
- Limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Veritas cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to LLT
- Limitations related to I/O fencing
- Limitations related to bundled agents
- Storage Foundation Cluster File System High Availability software limitations
- Storage Foundation for Oracle RAC software limitations
- Storage Foundation for Databases (SFDB) tools software limitations
- Storage Foundation software limitations
- Known issues
- Issues related to installation and upgrade
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Veritas File System known issues
- Replication known issues
- Cluster Server known issues
- Operational issues for VCS
- Issues related to the VCS engine
- Issues related to the bundled agents
- Issues related to the VCS database agents
- Issues related to the agent framework
- Issues related to Intelligent Monitoring Framework (IMF)
- Issues related to global clusters
- Issues related to the Cluster Manager (Java Console)
- VCS Cluster Configuration wizard issues
- LLT known issues
- I/O fencing known issues
- GAB known issues
- Operational issues for VCS
- Storage Foundation and High Availability known issues
- Storage Foundation Cluster File System High Availability known issues
- Storage Foundation for Oracle RAC known issues
- Oracle RAC known issues
- Storage Foundation Oracle RAC issues
- Storage Foundation for Databases (SFDB) tools known issues
- Issues related to installation and upgrade
Transaction hangs when multiple plex-attach or add-mirror operations are triggered on the same volume (3969500)
In an FSS or a CVM environment where the vol_intent_lock tunable is set to 1, an I/O count is taken on a volume each time a 'plex attach' or 'add mirror' operation is triggered. During this timeframe, if the same volume undergoes one more 'plex attach' or 'add mirror' operation, another transaction is triggered. This transaction waits for I/O count quiesce or drain. However, in some cases, the I/O count that is taken by previous 'plex attach' or 'add mirror' operation may not be handled correctly. In such a situation, the second 'plex attach' or 'add mirror' operation hangs and subsequently fails with the following transaction timeout error:
vxvm:vxconfigd: V-5-1-8011 Internal transaction failed: Transaction aborted waiting for io drain.
Workaround
Restart the master node.
Set the value of the vol_intent_lock tunable to 0 from the new master by using the following command:
# vxtune vol_intent_lock 0