Block Volumes for Roving Edge Infrastructure
Describes how to manage block volume tasks, including creating, updating, and deleting block volumes, on your Roving Edge Infrastructure devices.
You can perform the following block volume tasks:
The Block Volume service doesn't reserve storage space for block volumes and boot volumes in advance. Instead, storage space is consumed when the data is written to the block volume. For example, if a 100 GB block volume is created, it doesn't mean that 100 GB is reserved from the total available storage space for this block volume. The storage space remains available to all services and can be exhausted before the 100 GB volume is filled with data.
Also, the Block Volume service doesn't validate the specified size of a created block volume against the available storage space. This lack of validation can lead to over subscription when the total size of created volumes exceeds the storage space available on the device. Don't rely on block volume sizes to calculate storage space usage.
Plan the total storage needs of your Compute (boot volumes), Block Storage, and Object Storage resources in advance to ensure your storage doesn't exceed 80% of the total available storage. Then regularly monitor the available storage space to avoid oversubscription problems. If your storage capacities reach 80% or higher, see Avoiding Storage Overages Using Safe Mode.
See Overview of Block Volume in the Oracle Cloud Infrastructure documentation for more information on this service.