Please enter search query.
Search <book_title>...
Veritas Access Troubleshooting Guide
Last Published:
2021-02-14
Product(s):
Appliances (Version Not Specified)
Platform: 3340
- Introduction
- General troubleshooting procedures
- About general troubleshooting procedures
- Viewing the Veritas Access log files
- About event logs
- About shell-activity logs
- Setting the CIFS log level
- Setting the NetBackup client log levels and debugging options
- Retrieving and sending debugging information
- Insufficient delay between two successive OpenStack commands may result in failure
- Monitoring Veritas Access
- Common recovery procedures
- About common recovery procedures
- Restarting servers
- Bringing services online
- Recovering from a non-graceful shutdown
- Testing the network connectivity
- Troubleshooting with traceroute
- Using the traceroute command
- Collecting the metasave image of a file system
- Replacing an Ethernet interface card (online mode)
- Replacing an Ethernet interface card (offline mode)
- Replacing a Veritas Access node
- Replacing a disk
- Speeding up replication
- Uninstalling a patch release or software upgrade
- Troubleshooting the Veritas Access cloud as a tier feature
- Troubleshooting Veritas Access installation and configuration issues
- Troubleshooting the LTR upgrade
- Troubleshooting Veritas Access CIFS issues
- Troubleshooting Veritas Access GUI startup issues
- Index
Recovering from a non-graceful shutdown
In some cases, when a non-graceful shutdown of a node occurs (for example, during an unexpected system halt or power failure), you may receive an error message on the local node asking you to use the Linux fsck (file system check) command to repair files on the node.
To recover a node
- Login to the Management console (Veritas command-line interface) prompt.
- Run the following command:
storage>fs fsck <fsname>
where fsname is the name of the file system.
Once the file check is complete, you can continue to use the file system.