Info icon
End of Life Notice: For Trend Cloud One™ - Conformity Customers, Conformity will reach its End of Sale on “July 31st, 2025” and End of Life “July 31st, 2026”. The same capabilities and much more is available in TrendAI Vision One™ Cloud Risk Management. For details, please refer to Upgrade to TrendAI Vision One™
Logo of TrendAI
Use the Knowledge Base AI to help improve your Cloud Posture

Check for Clone Hydration Status

TrendAI Vision One™ provides continuous assurance that gives peace of mind for your cloud infrastructure, delivering over 1400 automated best practice checks.

Risk Level: Medium (should be achieved)
Rule ID: OCI-FileStorage-003

Ensure that cloned OCI File Storage file systems are fully hydrated before production workload deployment to avoid performance degradation from lazy loading and ensure maximum throughput. Hydration is the process in which metadata is copied from the source Snapshot to the clone, which is necessary for the clone to become a fully independent, performant file system.

Reliability

Deploying a production workload that requires peak performance before the clone is fully hydrated risks performance degradation due to this initial data-sharing and metadata-copying process. Ensuring the file system clone is fully hydrated minimizes this risk and allows the clone to operate at its expected maximum performance.

Audit

To determine if your OCI file system clones are fully hydrated, perform the following operations:

Using OCI Console

  1. Sign in to your Oracle Cloud Infrastructure (OCI) account.

  2. Navigate to File Storage console available at https://cloud.oracle.com/fss/.

  3. In the left navigation panel, choose File Systems, and select an OCI compartment from the Compartment dropdown menu, to list the file systems provisioned in that compartment.

  4. Click on the name (link) of the file system that you want to examine, listed in the Name column.

  5. Select the File System Information tab and check the Source Snapshot and Hydration attribute values to determine if the selected resource is a fully hydrated file system clone. If the Source Snapshot value contains the name of a snapshot (e.g., "Snapshot-20251105-1205-30"), check the Hydration attribute value. If the Hydration value is not Complete, the selected OCI file system clone is not fully hydrated.

Using OCI CLI

  1. Run iam compartment list command (Windows/macOS/Linux) with output query filters to list the ID of each compartment available in your Oracle Cloud Infrastructure (OCI) account:

    oci iam compartment list
	--all
	--include-root
	--query 'data[]."id"'

  2. The command output should return the requested OCI compartment identifiers (OCIDs):

    [
	"ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
	"ocid1.compartment.oc1..abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd"
]

  3. Run fs file-system list command (Windows/macOS/Linux) with the ID of the OCI compartment that you want to examine as the identifier parameter, to list the ID of each File Storage system provisioned in the selected OCI compartment:

    oci fs file-system list
	--compartment-id 'ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
	--availability-domain 'ABCD:AP-SYDNEY-1-AD-1'
	--all
	--query 'data[]."id"'

  4. The command output should return the requested file system IDs:

    [
	"ocid1.filesystem.oc1.ap_sydney_1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
	"ocid1.filesystem.oc1.ap_sydney_1.aaaabbbbccccddddabcdabcd1234abcd1234abcd1234abcd1234abcd1234"
]

  5. Run fs file-system get command (Windows/macOS/Linux) to determine if the selected OCI File Storage system is a file system clone:

    oci fs file-system get
	--file-system-id 'ocid1.filesystem.oc1.ap_sydney_1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
	--query 'data."source-details"."source-snapshot-id"'

  6. The command output should return the resource ID of the snapshot that was used to create the clone. If the command output returns a snapshot ID, as shown in the example below, continue the Audit process with the next step to get the hydration state for your file system clone:

    "ocid1.snapshot.oc1.ap_sydney_1.aaaabbbbccccddddabcdabcd1234abcd1234abcd1234abcd1234abcd1234abcd1234"

  7. Run fs file-system get command (Windows/macOS/Linux) to describe the hydration status for the selected OCI file system clone:

    oci fs file-system get
	--file-system-id 'ocid1.filesystem.oc1.ap_sydney_1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
	--query 'data."is-hydrated"'

  8. The command output should return the hydration status for the selected file system clone (true for complete, false for incomplete):

    false

    If the fs file-system get command output returns false, as shown in the example above, the selected OCI file system clone is not fully hydrated.

Remediation / Resolution

To ensure that OCI File Storage file system clones are fully hydrated for production use, you must simply wait for clone hydration to complete before deploying production workloads or consider pre-warming the clones. To pre-warm file system clones, perform the following operations:

Using OCI CLI

  1. After you mount the cloned OCI file system on a compute instance, run the following command (Linux) to sequentially read all files in order to trigger hydration. This initiates a recursive search and read operation for every file, forcing the lazy-loaded data blocks to copy immediately. Replace \<clone-mount-point\> with your own mounted clone directory:

    sudo find <clone-mount-point> -type f -exec cat {} > /dev/null \;

References

Publication date Nov 12, 2025

Related OCI-FileStorage rules