Veritas InfoScale™ 7.3.1 Release Notes - Linux
- Introduction
- Changes introduced in 7.3.1
- Changes related to installation and upgrades
- Changes related to the Cluster Server engine
- Changes related to Cluster Server agents
- Changes related to InfoScale in cloud environments
- Changes related to Veritas Volume Manager
- Changes related to Veritas File System
- Changes related to replication
- Changes related to Dynamic Multipathing
- System requirements
- Fixed Issues
- Known Issues
- Issues related to installation and upgrade
- Issues related to Veritas InfoScale Storage in Amazon Web Services cloud environments
- 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 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 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
Delayed allocation support extended to clustered file systems
The delayed allocation capability for extending writes on a file system was available for local mounts. This capability is now extended for clustered file systems (CFS mounts).
With this support, depending on an application I/O size, instead of allocating a single block for every write operation a clustered file system will now allocate multiple blocks in a single instance. The delayed allocation thus reduces the file system fragmentation.
When an application I/O is received, the delayed allocation capability enables the clustered file system to spilt the write operation in to the following sequence:
Reserve a disk space
When an application I/O is received, the file system first reserves a disk space and the data is cached.
Allocate extents
After a disk space is reserved, a scheduler allocates disk blocks at the background and the file system then combines multiple block allocation requests to allocate extents.
The delayed extent allocation thus helps to avoid file system fragmentation and keeps the extent contiguous even if several files grow at the same time.
The delayed allocation is not dependent on the file system disk layout version and is disabled by default. You can enable delayed allocation using the vxtunefs command. You can display the delayed allocation range in the file by using the fsmap command.
See the vxtunefs(1M) and fsmap(1M) manual pages.
Notes:
Delayed allocation must be disabled in cases where the data must be immediately written to the disk. For example, direct I/O, concurrent I/O, FDD/ODM access, and synchronous I/O.
Delayed allocation is not supported on memory-mapped files, BSD quotas, and shared mount points in a Cluster File System (CFS).
When BSD quotas are enabled on a file system, delayed allocation is turned off automatically for that file system.