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
In a CVM environment, adding a relabelled LUN to a shared disk group cause the I/O requests to fail until the LUN fails and disables the filesystem. (3979198)
In a CVM environment, when a relabelled LUN is added to a shared disk group, following error is logged in the /var/adm/messages
file for the same LUN until the LUN fails and disables the filesystem.
vxvm:vxconfigd: [ID 702911 daemon.notice] V-5-1-5249 ddl_detect_nonscsi : find_physical_path() fails for /dev/rdsk/<disk_name>
When a new LUN is added to a Solaris system dynamically, the operating system detects the device and creates an entry for the LUN. After relabelling the disk on one node, it may happen that the other nodes do not refresh the physical paths corresponding to the relabelled LUN. As a result, DMP continues to use the stale paths for the LUN on that node and cause the I/O requests to fail until the LUN fails and disables the filesystem.
Workaround:
If the disk size is less than 2TB, format the disk as SMI on each node. For larger disk size, format disk as EFI on each node. Ensure that each node has the same disk label format. That is, all nodes either have only SMI labels or only EFI labels.