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
Checking and repairing a file system
The Storage> fs fsck command lets you check and repair a file system while the file system is offline.
The Storage> fs fsck command tries to perform a normal fsck (check and repair) of the file system first, but if the fullfsck option is set, the command proceeds depending on the input that is provided by the user.
In most cases, a normal fsck (only log replay) is sufficient to repair a file system. In cases where there is structural damage to the file system's metadata, a full fsck of the file system may be necessary to repair the file system.
Warning:
Using the Storage> fs fsck command on an online file system can damage the data on the file system. Only use the Storage> fs fsck command on a file system that is offline.
Note:
When running the Storage> fs fsck command, you may encounter a process of Unknown. The Unknown process is normal, since there is no process printed as output when running a normal fsck using Storage> fsck fs name. Full fsck is run only if the normal fsck fails. In the support mode, if you are running a full fsck, Veritas Access records that status in an internal database/file.
To check and repair a file system
- To check and repair a file system, enter the following:
Storage> fs fsck fs_name
where fs_name specifies the file system for which you want to check and repair.