The Oracle ACFS file systems are automatically created when you create a shared repository, or when you create a database on Oracle Database Appliance.
However, the file systems do not initially consume all of the storage in the appliance which preserves space for additional repositories, or in some cases, database files stored directly in Oracle ASM. In Oracle Database Appliance software releases 12.1.2.2 and earlier, the Oracle ACFS file systems do not automatically extend if they run low on space, even if storage space is still available in the shared storage pool. You can check for available storage space in your file systems by running the operating system command df -h as shown in the following example.
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroupSys-LogVolRoot
30G 8.6G 20G 31% /
/dev/mapper/VolGroupSys-LogVolU01
97G 23G 70G 25% /u01
/dev/mapper/VolGroupSys-LogVolOpt
59G 6.8G 49G 13% /opt
/dev/sda1 99M 26M 68M 28% /boot
tmpfs 127G 1.2G 125G 1% /dev/shm
/dev/asm/datafsvol-352
5.0G 87M 5.0G 2% /odadatafs
/dev/asm/rdocdb1-66
5.0G 4.2G 874M 83% /u01/app/oracle/oradata/rdocdb1
/dev/asm/datcdb1-303
100G 4.2G 96G 4% /u02/app/oracle/oradata/datcdb1
/dev/asm/flashdata-138
558G 1.4G 557G 1% /u02/app/oracle/oradata/flashdata
/dev/asm/rcocdb1-352
132G 788M 132G 1% /u01/app/oracle/fast_recovery_area/rcocdb1
/dev/asm/acfsvol-352 50G 178M 50G 1% /cloudfs
/dev/asm/datastore-66
59G 4.3G 55G 8% /u01/app/oracle/oradata/datastore
/dev/asm/datastore-303
3.6T 2.1G 3.6T 1% /u02/app/oracle/oradata/datastore
/dev/asm/datastore-352
4.8T 10G 4.8T 1% /u01/app/oracle/fast_recovery_area/datastore
To extend the size of one of your file systems to accommodate growth in your data, you must manually expand the pool.
Refer to the following topics for more information:
oakcli resize dbstorage to expand space for database filesoakcli resize dbstorage
oakcli configure repo to expand shared repositories oakcli configure repo
My Oracle Support note 1437717.1 "Expanding /cloudfs File System."