Veritas InfoScale™ 7.2 Release Notes - Solaris
- 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.2
- Changes related to Veritas Cluster Server
- Changes related to installation and upgrades
- Changes related to Veritas Volume Manager
- Changes related to Veritas File System
- Changes related to Replication
- 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
- 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
- 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 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 |
---|---|
3871850 | When the disk detach policy is local and connectivity of some DMP node on which plex resides restores, reads continues to serve from only (n - 1) plexes, where n is total no of plexes in the volume |
3749245 | vxconfigd generated core dump while running stopnode/abortnode |
3873809 | vxconfigd died during command shipping due to improper string manipulation happening during shipping command for volume creation using enclosure as argument |
3874226 | layered DMP]vxdmpadm pgrrereg issue |
3875387 | vxassist core dump in add_dvol_plex_disks_hosts() |
3876230 | vxvol core generated while starting raid5 volume |
3876321 | IO hang seen on master node during ./cvm/cct/cvm/cvm_node_leave_join.tc#4 |
3876781 | Hitting ted assert volmv_cvm_handle_errmirs:1a during ./cvm/stress/cship/multicship/relayoutmultislaves.tc |
3877662 | ASSERT hit during vxdg move and vxdg expand operations for dg having opaque disks |
3879131 | noautoimport flag on standard disk doesn't get honored in presence of clone disk |
3879263 | Update diskgroup version and vx_ioparameters structure for Rufous |
3889443 | adding some extended stats in mirror volume IO code path (DRL logging, lock, sio-active) |
3890486 | Node panic while testing full instant snapshot on large node |
3890924 | Modifying VOL_TIME_JOIN* macros to log data to vxlogger infrastructure |
3891681 | VVR: DCM mode was no deactivated after resync was complete |
3892115 | vxconfigd dump during FSS DG destroy in ncopy_tree_build () due to NULL pointer dereference |
3892795 | vxdisk -o full reclaim takes more than 15+ minutes. Sometimes causes system hang |
3892816 | FSS DG creation failing with error "VxVM vxdg ERROR V-5-1-585 Communication failure with kernel" |
3892907 | /etc/vx/bin/vxresize works on invalid "-F <filesystem type>" as well |
3893323 | Handling UDID Mismatch when ASL has been changed the way it perceives UDID |
3894351 | vxlogger daemon support |
3894410 | vxdisksetup is failing intermittently in some TCs |
3894576 | vxdg adddisk reports successful exit status when run on an offline disk |
3895862 | VVR: Secondary Master node panic with secondary logging enabled |
3896537 | vxdefault command fails to set configuration default if the /etc/default directory does not exist |
3897429 | Repeated/duplicate logging in voldctlmsg.log |
3897652 | Make SAL device Map operation persistent so that DG auto-import would work on mapped SAL devices |
3898514 | Avoid adding STUB device in connectivity hash table |
3898653 | Node panics after master switch and slave rejoin while IO's are running in parallel |
3898732 | Node panic'd while running recovery/plex attach operation on volume. |
3899631 | Man page and help message change for "vxdisk -o mfd list" |