Veritas InfoScale™ 7.4.2 Release Notes - Linux
- Introduction
- Requirements
- Changes introduced in 7.4.2
- Changes related to installation and upgrades
- Changes related to security features
- Changes related to supported configurations
- Changes related to the Cluster Server engine
- Changes related to Cluster Server agents
- Changes related to Veritas Volume Manager
- Changes related to Veritas File System
- Changes related to replication
- Fixed issues
- 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
- 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
- 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
- Cloud deployment known issues
- Issues related to Veritas InfoScale Storage in Amazon Web Services cloud environments
- Issues related to installation and upgrade
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 |
---|---|
3868154 | If DMP native support is set to ON, the vxdmpadm native ls command incorrectly displays the volume group information when multiple volume groups exist on a disk. |
3915523 | When a private disk group is imported with its name, a remote disk is created for it even though the disk does not belong to the same disk group. |
3969860 | The event source daemon, vxesd, takes a long time to start when several LUNs (around 1700) are attached to the system. |
3899568 | The DMP |
3907596 | The vxdmpadm setattr command reports an error when it sets the path attribute. |
3925345 | The vxvolgrp command inadvertently created thousands of empty |
3931048 | VxVM creates some log files and incorrectly assigns the write permission to all the users. |
3958114 | Read operations on a subordinate node are 50% slower than those on a master node. |
3959986 | A memory management issue with |
3955979 | I/O operations became unresponsive during synchronous replication. |
3973364 | If network lags occur when the synchronous mode of volume replication is used with TCP, I/O operations may become unresponsive for as long as 15-20 minutes. |
3972679 | vxconfigd failed to start because it accessed an invalid address and caused a memory segment fault. |
3964964 | Performance issues occurred due to soft lockup of vxnetd. |
3978330 | The values of the VxVM and the VxDMP tunables do not persist after a system restart with 4.4 and later versions of the Linux kernel. |
3947265 | The vxvm-startup script includes a delay for the discovery of Infiniband devices, which causes vxfen to fail and eventually causes a split-brain situation. |
3975405 | cvm_clus fails to stop even after hastop -all is triggered and causes the cluster nodes to get stuck in the LEAVING state. |
3982690 | After a system restart, the vxconfigd process fails to come online in a CVM environment. |
3983803 | The vxsnap command fails with a core dump. |
3983821 | A cluster node panics during the readback process. |