Please enter search query.
Search <book_title>...
Veritas Access Release Notes
Last Published:
2020-10-16
Product(s):
Access (7.4.2)
Platform: Linux
- Overview of Veritas Access
- Fixed issues
- Software limitations
- Flexible Storage Sharing limitations
- Limitations related to installation and upgrade
- Limitation related to replication
- Known issues
- Veritas Access known issues
- Admin issues
- Backup issues
- CIFS issues
- Deduplication issues
- FTP issues
- General issues
- GUI issues
- Installation and configuration issues
- Internationalization (I18N) issues
- Networking issues
- NFS issues
- ObjectAccess issues
- OpenDedup issues
- OpenStack issues
- Replication issues
- SDS known issues
- SmartIO issues
- Storage issues
- System issues
- Target issues
- Upgrade issues
- Veritas Data Deduplication issues
- Veritas Access known issues
- Getting help
In an erasure-coded file system, when the nodes are restarted, some of the file systems do not get unmounted
When the number of faulted nodes exceeds the given tolerance limit for an erasure-coded file system, it is expected that the cfsmount resources should go into the FAULTED state and the file systems should be unmounted properly on the remaining nodes. But some of the file systems do not unmount on the remaining nodes after the nodes are restarted.
Workaround:
Manually bring the file systems offline on the remaining nodes using the Veritas Access command-line interface. As the file systems are in the disabled state, unmount and mount the file systems after the faulted nodes are back online.