OCI Block Volume Mount scenarios with 'Device is Busy' scenarios Despite Unmount Attempts
I'm relatively new to this, so bear with me... I'm stuck on something that should probably be simple. I'm currently working with an scenario when trying to unmount and detach a block volume from an OCI instance... I have a compute instance running Oracle Linux 8, and I attempted to detach a block volume after ensuring it was unmounted. However, I'm receiving the following behavior when I try to detach it using the OCI CLI: `behavior: Device is busy`. I've checked the mounted devices with `lsblk`, and the volume is not listed as mounted, yet the CLI insists it is busy. I tried the following steps to troubleshoot: 1. Verified no processes are using the block volume with `lsof` and `fuser`, but they don't show any active connections. 2. Run `sync` to flush filesystem buffers, thinking there might be lingering operations. 3. Attempted to force unmount the volume with `umount -l /dev/xyz`, but it still doesn't resolve the scenario. 4. Finally, I rebooted the instance, hoping it would release any locks, but the same behavior occurred upon trying to detach again. Here’s how I initially attached the block volume: ```bash oci bv volume create --availability-domain <AD> --compartment-id <COMPARTMENT_ID> --size-in-gbs 50 --display-name my_volume oci compute volume-attachment create --instance-id <INSTANCE_ID> --volume-id <VOLUME_ID> --type paravirtualized ``` And to mount it, I used: ```bash sudo mkdir /mnt/my_volume sudo mount /dev/xyz /mnt/my_volume ``` Now, I’m at a loss for what else I can do to detach this block volume. Has anyone encountered this scenario before? Any suggestions would be greatly appreciated! This is part of a larger API I'm building. The stack includes Bash and several other technologies. Is this even possible? Has anyone dealt with something similar?