Usando AWS re:Post, accetti AWS re:Post Termini di utilizzo
AWS re:Postre:Post

Started detaching volume by mistake - how to cancel

0

Hi,

I started detaching an EBS volume by mistake (I chose the wrong volume).

Since the volume was still mounted it has not detached and is now stuck in a "busy" state.

It still works fine but if the instance is rebooted at any time then I'm worried it will detach and this might happen when I am not around to sort it out.

Is there any way to cancel the detach instruction and get the volume back in a normal "attached" state?

Thanks and regards

Argomenti
Archiviazione
Tag
Amazon Elastic Block Store
Lingua
English
rePost-User-8611036
posta un anno fa359 visualizzazioni
1 Risposta
0

How about setting it to automatically mount after reboot?
The following document describes how to set it up.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html#ebs-mount-after-reboot

With this setup, if you accidentally detach it, it will be restored after attaching and rebooting.

profile picture
ESPERTO
Riku_Kobayashi
con risposta un anno fa
  • rePost-User-8611036
    un anno fa

    Thanks. That article contained some great info I was not aware with, such as mounting devices using their UUID. I do already have an fstab file to mount the volume on reboot, was hoping though I could "cancel" the detach instruction so that I don't have a service interruption while I unmount and mount again (or reboot and mount again). Was also hoping the detach instruction would time out since the volume is still mounted but seems there is no timeout and the "busy" state persists forever until an unmount or reboot happens.

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande

Contenuto pertinente