Please enter search query.
Search <book_title>...
Veritas InfoScale™ 7.0 Release Notes - Solaris
Last Published:
2017-12-18
Product(s):
InfoScale & Storage Foundation (7.0)
- 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
- 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
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Dynamic Multi-Pathing 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
- Storage Foundation software limitations
- Documentation
vxmirror to SAN destination failing when 5 partition layout is present: for example, root, swap, home, var, usr (2815311)
The vxmirror command may fail with following error on a Solaris 10 host, for a thin LUN, if more than one partition excluding root and swap is present.
VxVM vxbootsetup WARNING V-5-2-5667 Max volume count 5 exceeded.
Example
# /etc/vx/bin/vxmirror" -f -g rootdg_17_23_49 rootdisk01 rootdisk02 ! vxassist -g rootdg_17_23_49 mirror swapvol rootdisk02 ! vxassist -g rootdg_17_23_49 mirror rootvol rootdisk02 ! vxassist -g rootdg_17_23_49 mirror usr rootdisk02 ! vxassist -g rootdg_17_23_49 mirror var rootdisk02 ! vxassist -g rootdg_17_23_49 mirror home rootdisk02 ! vxbootsetup -g rootdg_17_23_49 VxVM vxbootsetup WARNING V-5-2-5667 Max volume count 5 exceeded. VxVM vxbootsetup ERROR V-5-2-5678 Skipping volume 'home_dcl' because no free partitions are available on disk 'disk_0'. Either remove the volume or make a partition available VxVM vxbootsetup WARNING V-5-2-5667 Max volume count 5 exceeded. VxVM vxbootsetup ERROR V-5-2-5678 Skipping volume 'usr_dcl' because no free partitions are available on disk 'disk_0'. Either remove the volume or make a partition available VxVM vxbootsetup WARNING V-5-2-5667 Max volume count 5 exceeded. VxVM vxbootsetup ERROR V-5-2-5678 Skipping volume 'var_dcl' because no free partitions are available on disk 'disk_0'. Either remove the volume or make a partition available /usr/lib/vxvm/bin/vxmksdpart: 3pardata0_2492: is not an identifier