Setting a File System's Reported Size
Learn how to set a File Storage file system's reported size through a mount target.
The File Storage service reports file system capacity as 8589934592 gibibytes (GiB) and 8589934592 gibiinodes (GiI) by default. Sometimes, application installers perform a space requirement check before running an installation process but can't correctly interpret the reported size or reported inodes of the file system. When this occurs, you can define the file system size reported to the OS by setting the Reported Size or Reported Inodes value in the file system's mount target. Typically, setting the size to 1024 GiB and the inodes to 1024 GiI permits successful installation.
Changing the Reported Size or Reported Inodes for a mount target affects all file systems exported by the mount target. Changing these values doesn't limit the amount of data you can store.
There can be a delay of up to 1 hour when reporting file system usage, either in the Console or by using the
df command. For more information, see File System Usage and Metering. - Open the navigation menu and select Storage. Under File Storage, select Mount Targets.
- In the List scope section, under Compartment, select a compartment.
- Click the name of the mount target that you're interested in.
- On the mount target's details page, click the Reported Size (GiB) or the Reported Inodes (Gil) edit icon.
- Enter the maximum size in gibibytes or the maximum inodes in gibiinodes you want the File Storage service to report.
- Click the Save icon.
Use the
fs export-set updatecommand and required parameters to set the reported size of the file system made available through the mount target's exports:oci fs export-set update --export-set-id <export_set_ OCID> --max-fs-stat-bytes <number_of_bytes>For a complete list of parameters and values for CLI commands, see the CLI Command Reference.
Run the UpdateExportSet operation to change the reported size of a file system.
For information about using the API and signing requests, see REST API documentation and Security Credentials. For information about SDKs, see SDKs and the CLI.