Veritas Access Release Notes
- 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
Scale-out file system returns an ENOSPC error even if the df command shows there is space available in the file system
A scale-out file system returns an ENOSPC error even if the Linux df command shows there is space available in the file system.
This situation can happen in one of the following cases:
A scale-out file system uses a hashing algorithm to distribute data between the storage containers. The algorithm makes sure that data is evenly distributed between all the containers, and depending on the type of the data, one of the storage containers is used more often than the other containers. A scale-out file system can reach 100% usage early. In this scenario, any allocation going to the 100% full container returns an ENOSPC error.
A scale-out file system constitutes a metadata container and multiple data containers. Space for the metadata container is allocated at the time of creation of the file system. If the data containers are all full and the metadata container has available space, then the file system does not use the space in the metadata container. Because of this, the Linux df command can show there is still available space, but applications see an ENOSPC when writing to the file system.
Workaround:
Grow the file system.