A block volume has its own identity, location and capacity settings. It is separate from the instance that may later use it. Read the required Availability Domain and supplied volume OCID before changing capacity or performance intent. A similarly named resource isn't a safe maintenance target.
These original tasks create and expand local volume records. Their values are assigned exercise settings, not provider prices or throughput guarantees. The model supports a small performance subset and growth within its documented range. It doesn't allocate a real block device or resize a guest filesystem. A production expansion needs the current supported procedure and appropriate guest, application and data checks before the new capacity is considered usable.
Verify the volume identifier, Availability Domain and requested capacity separately.