Veritas InfoScale™ 7.3 Release Notes - Linux
- About this document
- Important release information
- About the Veritas InfoScale product suite
- Licensing Veritas InfoScale
- About Veritas Services and Operations Readiness Tools
- Changes introduced in 7.3
- Changes related to Veritas Cluster Server
- Changes related to Veritas Volume Manager
- Changes related to Veritas File System
- Changes related to virtualization
- Changes related to replication
- Changes related to operating systems
- Changes related to Veritas Cluster Server
- System requirements
- Fixed Issues
- Known Issues
- Issues related to installation and upgrade
- Issues related to Veritas InfoScale Storage in Amazon Web Services cloud environments
- 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
- 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
- Application isolation feature 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
- 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 for Sybase ASE CE software limitations
- Documentation
Veritas Volume Manager fixed issues
This section describes the incidents that are fixed related to Veritas Volume Manager (VxVM) in this release.
Table: Veritas Volume Manager fixed issues
Incident | Description |
---|---|
3914790 | Nodes in the cluster panic when map allocation information is transferred from an old DCO to a new DCO. |
3915202 | The VxVM configuration daemon freezes during re-initialization of VxVM volumes |
3914535 | The CVMVolDg resource fails to come online within the expected time as the disk group import operations fails with the following message: Disk group exists and is imported |
3913545 | The primary node panics due to a premature async update on a volume when DRL flushing is in progress. |
3913489 | I/O operations freeze on secondary node due to conflicting lock issues. |
3913382 | The VxVM configuration daemon freezes when nodes leave the cluster. |
3912216 | The Master and slave nodes panic when VxVM switches the master node and the slave node leaves the cluster. |
3910027 | Nodes panic during upgrade due to issues with the storage access layer protocol. |
3907565 | The disk configuration operation by the vxdisksetup command on SAMSUNG SSD_DISK causes the disk to go into an error state. |
3903028 | The CVM node fails to join the second sub-cluster after the first phase of rolling upgrade completes. |
3898455 | : node panic while running ./scripts/recovery/srl_holes_dbg.tc as dummy update is not allocated same sized mlist on primary & secondary |
|