Veritas InfoScale™ 7.0 Release Notes - Linux
- About this document
- Important release information
- About the Veritas InfoScale product suite
- Licensing Veritas InfoScale
- About Symantec Operations Readiness Tools
- Changes introduced in 7.0
- Licensing changes for InfoScale 7.0
- Changes related to installation and upgrade
- System requirements
- Fixed Issues
- Known Issues
- Issues related to installation and upgrade
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Virtualization 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
- Cluster Server agents for Volume Replicator known issues
- 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
- Storage Foundation for Sybase ASE CE known issues
- Issues related to installation and upgrade
- Software Limitations
- Virtualization software 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
- Cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- 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 for Sybase ASE CE software limitations
- Documentation
VCS fails to stop volume due to a transaction ID mismatch error [3292840]
If VCS imports a disk group A on node sys1, which implies that the DiskGroup resource is online on sys1. If you run vxdg -C import <dg_name> outside VCS on node sys2, then the disk group gets imported on node sys2 and -C clears the import locks and host tag. However on node sys1, disk group A continues to appear as imported and enabled, and hence, VCS continues to report the resource state as ONLINE on node sys1. Subsequently, when VCS detects the imported disk group on sys2, it deports the disk group from sys2, and imports it on sys1 to resolve concurrency violation. At this point, the disk group deported from node sys2 is shown as imported and enabled on node sys1. If you stop any volume from within or outside VCS, it fails with the Transaction ID mismatch error, but the read and write operations continue to function so the data continues to be accessible. This situation may lead to data corruption if the disk group appears enabled on multiple nodes. This issue is due to the Volume Manager behavior.
Workaround: Do not import a disk group using -C option if that diskgroup is under VCS control.