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
Decreasing the size of a file system
You can decrease (shrink) the size of the file system.
Note:
For a scale-out file system, you can decrease the size of the primary tier only.
See About scale-out file systems.
To decrease the size of the file system, it must be online. If the file system is not online, an error message is displayed, and no action is taken.
You cannot decrease the size of a file system if a rollback exists. Delete the rollback first before using the Storage> fs shrinkto or Storage> fs shrinkby commands.
To decrease the size of a file system to a specified size
- To decrease the size of a file system, enter the following:
Storage> fs shrinkto {primary|secondary} fs_name new_length
To decrease the size of a file system by a specified size
- To decrease the size of a file system, enter the following:
Storage> fs shrinkby {primary|secondary} fs_name length_change
primary | secondary
Specifies the primary or the secondary tier.
fs_name
Specifies the file system whose size decreases. If you specify a file system that does not exist, an error message is displayed.
new_length
Specifies the size to decrease the file system to. The size that you specify must be a positive number, and it must be smaller than the size of the existing file system. If the new file system size is not smaller than the size of the existing file system, an error message is displayed, and no action is taken.
length_change
Decreases the file system by a specified size. The size that you specify must be a positive number, and it must be smaller than the size of the existing file system. If the new file system size is not smaller than the size of the existing file system, an error message is displayed, and no action is taken.
Note:
Decreasing the size of a file system can take a long time if there are many extents allocated in the shrink area, as these extents have to be relocated to other areas in the file system.