Veritas InfoScale™ 7.1 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.1
- Changes related to Veritas Cluster Server
- Changes in the Veritas Cluster Server Engine
- Changes related to installation and upgrades
- Changes related to Veritas Volume Manager
- Changes related to Veritas File System
- Changes related to Dynamic Multi-Pathing
- Changes related to Replication
- Not supported in this release
- Technology Preview: Application isolation in CVM environments with disk group sub-clustering
- Changes related to Veritas Cluster Server
- 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
- 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
- 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
- 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 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 File System fixed issues
This section describes the incidents that are fixed related to Veritas File System (VxFS) in this release.
Table: Veritas File System fixed issues
Incident | Description |
---|---|
3708836 | fallocate causes data corruption. |
3811849 | System panics in lookup() in a directory with large directory hash (LDH). |
3762125 | Directory size increases abnormally. |
3633683 | VxFS thread consumes high CPU while running an application that makes excessive sync() calls. |
3833816 | Read returns stale data on one node of the CFS. |
3803803 | After the node restarts, VIPs may be online before all the share resources are online. |
3736398 | NULL pointer dereference panic in lazy unmount. |
3866962 | Data corruption is seen when dalloc writes are going on the file and simultaneously fsync started on the same file. |
3695367 | Cannot remove the volume from multi-volume VxFS using t he fsvoladm(1M) command. |
3731844 | The umount -r option fails for VxFS 6.2 with error "invalid options". |
3838625 | The tier schedule sync command fails. |
3856363 | File system inodes have incorrect blocks. |
3558087 | "ls -l" hangs while taking backup. |
3872964 | System hangs on SFHA 6.2.1/RHEL6.7. |