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
While creating an erasure-coded file system, a misleading message leads to issues in the execution of the storage> fs create command
When you create an erasure-coded file system using the Storage> fs create command, the following content appears as part of the help message:
eclogdisk : comma separated list of disks from at least ndata+nparity failure domains to be used for EC log allocation. To use default disks, pass eclogdisk=default []
This message is misleading and if you specify eclogdisk=default as an option, the command does not get executed successfully.
Workaround:
Ignore the help description for eclogdisk. Pass the value for eclogdisk as "default" instead of eclogdisk=default when you create a file system.