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
Removing disks from the pool fails if a DCO exists
If you specify disks on the Veritas Access command line when you create a file system, Veritas Access might create a data change object (DCO) on disks other than those specified. If free disks are available in the pool, Veritas Access prefers those for the DCO. The DCO is required to handle synchronization between the mirror and the original volume. The DCO is used when a disk that contains the data volume fails.
If you try to remove the disk from the pool, the following error displays because the disk is in use by the DCO.
SFS pool ERROR V-288-2891 Disk(s) sde are used by the following: DCO of primary tier of fs_mirror, Primary tier of filesystem fs_mirror
Workaround:
There is no workaround.