Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Configuring an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
Determining the initial extent size for a file system
Veritas File System (VxFS) determines the size of the first extent that is allocated based on the first write to a new file. Normally, the first extent is the smallest power of 2 that is larger than the size of the first write. If that power of 2 is less than 8 KB (the default file system block size), the first extent that is allocated is 8 KB. After the initial extent is allocated, the file system increases the size of subsequent extents with each allocation as the file size is increased using extending writes.
The initial extent size is tunable, and can be changed using the System> option modify tunefstab command.
Increasing the initial extent size to a larger value helps to reduce file system fragmentation and improves I/O performance.
The best value for the initial extent size depends on the expected file sizes that are created by the application. The maximum value is 32768, which equates to a 256 MB extent allocation using the default 8 KB file system block size. Any over allocation of space is returned to the free space pool after the file is closed.
If the application creates a lot of small files with an exact size of 1 MB, then the initial extent size can be set to 128 (1 MB). If 1 MB is an approximate file size, then the initial extent size can be set to 64 (512 KB) instead. If most files are approximately 1 GB or greater in size, then the maximum value of 32768 can be used.