Issues with a specific volume

Questions / Help
,
1

Dear staff,

The volume vol_vw2lm902em37q18v (ams, ed57) was attached to a temporary machine (launched with --rm flag). On May 21, the machine disappeared and the volume entered the pending_destroy state. I guess it was a hardware failure.

However, I now see 2 issues:

  • The volume is stuck as pending_destroy and its size still counts as used, both in Apps dashboard and in Billing usage breakdown.

  • I noticed that a new volume (vol_4ml0em751xxx3ozv, ams, 1192) was added to this app without any action from my side. This was unexpected. I did not realize that the system could create billable resources automatically.

Would you please help me figure out what happened? Could this have been an unsuccessful migration to new hardware? How to remove the broken volume?

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.